OSS + ELC EU 2026

Silent failures in MCP tool invocation aren't random. They trace back to a single root cause: tool descriptions that are too vague for agents to reliably select the right tool.
A SAIL Research study of 856 tools across 103 MCP servers found 97% have at least one quality defect, 56% fail to clearly state what the tool does, and 89% provide no guidance on when not to use it. A second study of 10,831 servers confirmed that well-written descriptions get selected 260% more often, improving task success rates by ~6 points.
Working with the Glama founder, I developed TDQS (Tool Definition Quality Score) : an open-source framework scoring MCP tools across six dimensions: Purpose Clarity, Usage Guidelines, Behavioral Transparency, Parameter Semantics, Conciseness, and Contextual Completeness.
This talk covers how TDQS was built, what scoring thousands of real-world servers revealed, and how the open-source community can adopt it as a quality standard for MCP tool authorship.