Cutting MCP Server Tool Count From 15 to 4 to Reduce Token Overhead
A developer found that every tool exposed by an MCP server sends its name, description, and JSON Schema to the model on each request, adding significant token cost. Their 15-tool file-management server had a system prompt of about 4,800 tokens before any user input. They consolidated the surface into four core primitives (read, write, list, search) plus a rarely-invoked help meta-tool, lowering the baseline to roughly 1,100 tokens. The change also made the agent faster and cheaper, since the model had fewer options to reason over. The article includes a protocol-shaped example server to illustrate the approach, though it is not a full implementation of the official MCP SDK.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in