Airia Radar routes only the tools each call needs
Covered by Signal Brief for B2B SaaS product managers — one of 5 tools in Issue #13 · airia.com
What it does
Airia on Wednesday shipped a major upgrade to its MCP Gateway aimed at the problem every enterprise agent rollout hits after the demo: tool sprawl. The math is brutal. Every tool connected through MCP sends its full description into the model’s context window on every call, so an organization with 200 available tools pays for all 200 on every interaction — Airia has observed organizations loading 250 or more tool definitions per call — and every loaded description is noise competing with the actual query, degrading accuracy before any productive work happens. A single API catalog can generate an MCP server with 1,500 endpoints, which until now meant manual curation: capability sacrificed before deployment even starts. Airia’s answer is Radar, an intelligence layer that replaces the loaded catalog with three lightweight native tools as the only defaults — Search, Execute, and Manage Cache. When an agent issues a query, it calls Search, which runs a semantic match across every tool in the gateway regardless of size and returns the most relevant options; the agent selects what it needs and executes, and those tools are cached automatically, retrieved instantly on subsequent calls. The cache builds from actual usage with no pre-configuration, and Airia absorbs the cost of every Radar call internally. The release also expands the catalog to nearly 2,000 pre-configured servers; adds a Dynamic MCP Gateway where one address serves every user a personalized, role-based toolset — including discovery that finds local MCP configurations on employee devices and replaces them automatically, so a new hire’s AI client is pre-configured on day one; supports the formal MCP extension for Skills; and annotates every tool semantically — read-only, destructive, or otherwise — with a prompt-injection scan status, filterable by admins building gateway configurations. Every major MCP client is supported, including Claude Code, Cursor, and Codex. Available now for all Airia customers.
Why it matters for PMs
Context is a budget line, and this release is the clearest statement yet that just-in-time discovery — not bigger windows — is how enterprise agent stacks will scale. Three implications. First, if you expose your product through MCP, you are now one of potentially thousands of tools behind your customers’ gateways: semantic discoverability, a clean description, and honest annotations (read-only versus destructive) are becoming conversion assets the way app-store metadata was. Second, the gateway is a distribution layer, not just a security control — one configuration change rolls a tool out to 500 engineers, and being easy to adopt org-wide is a GTM asset worth designing for. Third, the economics: tool descriptions loaded but never used are pure overhead, and “context efficiency” is on its way to becoming a procurement question alongside latency and price. For your own agent features, the pattern to copy is Radar’s: don’t hand the model everything you have; let it ask for what it needs, and cache the answers.
The link Signal Brief published for this tool in Issue #13.
The other 4 tools in Issue #13
5 tools like these, every weekday before standup.
Join Signal Brief for $10/month or $96/year — every tool with why it matters for PMs and a direct link. No sponsors, no noise.
Start your 7-day free trialNo card required to start. Cancel anytime.