Oriel — AI & technology worth noticing, every day.

MCP Token Cost: I Cut My MCP Server From 15 Tools to 4

Post · https://dev.to/aws-builders/mcp-token-cost-i-cut-my-mcp-server-from-15-tools-to-4-cek

I rebuilt a real AWS cost-triage MCP server from 15 tools to 4. Same account, same question, 7 tool calls down to 2, schemas 88% smaller.

First seen by Oriel on .

AI summary

A practical A/B rebuild of a read-only AWS cost-triage MCP server shows that outcome-level tool design reduced 15 tools to four while preserving findings and pricing capabilities.

  • The bloated version used thin boto3 wrappers and required seven calls to inspect volumes, addresses, snapshots, instances, NAT gateways, load balancers, and identity.
  • The lean version combines checks in find_waste, constrains inputs with Literal types, returns limited fields by default, provides lazy taxonomy, and reports actionable errors.
  • Tool-description size fell from 7,898 to 897 characters, tool calls dropped from seven to two, and both versions returned the same three resource IDs.
  • The server identified an unattached 8 GiB gp2 volume, an orphaned 8 GiB snapshot, and an unassociated Elastic IP whose savings remained unverified.
  • Kiro's context tool budget only declined from 1.1% to 0.8% in this small demo, while the author argues larger benefits emerge with production-scale tool counts.

#mcp #aws #token optimization #ai agents

Generated by gpt-5.6-sol. Check the original for details.

Metric trends

Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained

Reactions

Total public reactions reported by the source; distinct from points and likes.

  • DEV Community: 82, latest observation ; +51 over observed period since

Comments

Comment count reported by the source.

  • DEV Community: 95, latest observation ; +62 over observed period since

Aliases

SourceExternal IDURL
DEV Community4883971https://dev.to/aws-builders/mcp-token-cost-i-cut-my-mcp-server-from-15-tools-to-4-cek Read discussion