You may be able to reduce context usage by having one tool that can leverage multiple API endpoints behind the scenes. This abstraction layer is one of the benefits of MCP.
I could do the same with REST where I create an LLMs' BFF that does all of the aggregations for me so that only the data the LLMs need are returned ;) We already do that for mobile app clients, so LLMs are just another type of clients IMO.
Another approach is to let the LLM explore the MCP on its own but then have it write a simple CLI program which aggregates MCP calls for common workflows so that we don't have to instruct it again and again with Markdown files of how to chain the calls together which it would get right about 80% or less of the time.
Another approach is to let the LLM explore the MCP on its own but then have it write a simple CLI program which aggregates MCP calls for common workflows so that we don't have to instruct it again and again with Markdown files of how to chain the calls together which it would get right about 80% or less of the time.