Where is the MCP client located within the project structure?	Inside the mcp-client.py file in the root project directory.
What is the primary function of the MCP client class?	To wrap the client session and expose server functionality to the rest of the codebase.
What does the client session represent?	The actual connection to the MCP server, which is part of the MCP Python SDK.
Why might the MCP client class contain a large amount of code?	It includes necessary resource cleanup code for the client session.
What is the purpose of the `list_tools` function?	To retrieve and return a list of all tools implemented by the MCP server.
What arguments does the `call_tool` function accept?	The name of the tool and the input parameters/arguments for that tool.
What is the key structural difference between an MCP tool definition and a Bedrock JSON schema?	The MCP spec has its own definition, which is slightly different from the Bedrock expected structure.
Where is the translation from MCP tool definitions to the Bedrock format handled?	In functions like `to_bedrock_tools` located within the `bedrock.py` file.
What is the common practice when using the client session?	Wrapping the session inside a larger class to manage resources and cleanup.
What is the ultimate goal of implementing `list_tools` and `call_tool` in this project?	To allow Claude to inspect documents and execute tools provided by the MCP server.