MCP Dev Summit Seoul 2026

We built an MCP server exposing 40+ operations. Agents misused most of them. Hybrid search returned only IDs with no context. get_issue prefixed every field with redundant key-value labels, burning tokens without helping the LLM. We had write tools with no corresponding read tools. Custom field schemas varied wildly across organizations, causing unpredictable bloat.
We cut to 14 tools. Agent precision improved dramatically. But deciding which 14 - and how to design them - required building a framework we wish had existed when we started.
This talk shares that framework as an open, reusable methodology any MCP server author can apply: how to audit which tools agents actually select vs. misuse, how to score agent success rate per tool, how to identify tools that confuse rather than help, how to structure response shapes for minimal token cost and maximum agent comprehension, and how to design progressive disclosure so capability scales without overwhelming context.
Every team building an MCP server faces this decision. We'll give them a starting point so they don't have to learn it the hard way.