What is the primary purpose of implementing custom prompts within an MCP server?	To provide highly tailored, evaluated prompts that ensure a high-quality, specialized result for a specific use case, surpassing what a user could manually request.
What feature is being added to the MCP server to allow users to interact with prompts?	Support for slash commands (e.g., `/format`).
What is the specific goal of the `/format` command in the MCP server?	To instruct Claude to reformat a plain text document into Markdown syntax.
When a user triggers a prompt via the client, what data structure does the MCP server send to Claude?	A list of messages, which includes actual user and assistant messages.
What syntax is used to define a prompt within the MCP server?	The prompt decorator, similar to how tools and resources are defined.
What are the required components when defining a prompt in the MCP server?	A name for the prompt and an optional description.
What information does the prompt function receive as an argument during execution?	Arguments passed by the client, such as a document ID.
What is the overall workflow that the defined prompt instructs Claude to execute when reformatting a document?	Fetch the document content using a tool, rewrite it in Markdown, and then edit the document to save the updates.
Why is it beneficial to define prompts within the MCP server rather than just putting them in the client code?	It allows the server to expose high-quality, pre-evaluated prompts that clients can use without needing to understand the underlying process.
What is the current state of document content within the MCP server before the reformatting process?	Plain text, without any special formatting.