What is the purpose of implementing `list prompts` in the MCP client?	To allow the client to list all defined prompts available on the MCP server.
How is the `list prompts` functionality implemented in the MCP client?	By calling `self.session.list_prompts()` and returning `result.prompts`.
What two pieces of information are required by the `get prompt` function?	The prompt name and a set of arguments.
How are arguments used when retrieving a prompt?	They are passed as keyword arguments to the prompting function and used to interpolate values within the prompt.
What specific data structure does the `get prompt` function return?	`result.messages`, which represents the conversation to be fed into "cloud."
In the overall prompt workflow, what is the role of the MCP server?	It is where the prompt is defined, and the client requests it with necessary arguments.
When a user invokes a prompt via the CLI, what is fed directly into "cloud"?	The prompt (the user message) and any necessary document IDs or arguments.
What is the expected outcome when a prompt is used to reformat a document?	The system fetches the document content (using a tool like `get document`) and "cloud" responds with the reformatted output.