AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with custom-built or unnamed agent Oct 26, 2026
Triage AWS costs with a slimmer MCP server
Author rebuilt an AWS cost-triage MCP server from 15 tools to 4, cutting a question from 7 tool calls to 2 with schemas 88% smaller. · Oct 26, 2026
- What They Did
- The author built a read-only AWS cost-triage MCP server twice, once as 15 thin boto3 wrappers and once as 4 outcome-level tools. Both ran in Kiro against the same real account, asked where money was being wasted. The lean version has a find_waste tool that runs the checks internally and returns five fields per finding. It also has constrained parameters and a separate estimate_savings tool.
- How It Went
- The bloated server needed 7 calls and the lean one 2. Tool descriptions shrank 88% (7,898 to 897 characters), and both found the same three wasted resources. The Elastic IP cost stayed unverified.
- Worth Knowing
- On this small demo, Kiro's context meter only moved from 1.1% to 0.8%, so expect big savings only with many tools.
Try it yourself with custom-built or unnamed agent
Review my MCP server in [path to project] that exposes [number] tools for [e.g. AWS cost data]. Propose a slimmer design that merges overlapping tools into as few as possible, trims the schemas, and still answers questions like [example question]. Show me the plan and the before and after tool counts before editing any files, then implement it and compare the number of tool calls on that question.
Do this with a skill.
These AI Services Market playbooks do this exact job.