NetBox is only a source of truth if it still matches the network. Here is how one natural-language instruction reconciles a live UniFi controller against NetBox, writes only the differences, and proves the boring but important property: when nothing has drifted, it changes nothing.
One discovery call on our production gateway returned ~320 KB of TypeScript declarations — roughly 80,000 tokens gone before the agent had done anything. Here is how we fixed tool discovery at enterprise scale with tiered output, 200 lines of BM25, and no vector database.
Your NetBox says one thing, your switch says another. Here is how to reconcile them with a single natural-language instruction instead of a Python script you have to maintain forever.
Xen Orchestra 6.4 stabilized its REST API and 6.5 added PATCH updates and VM controllers. Vates ships a first-party MCP server — 7 tools, read-only by design. We took a different cut: the entire 245-endpoint surface, read and write, as one DADL. Both belong in the same registry. Here is why.
How an Enterprise Tool Library actually works: the six pillars, the fail-closed request pipeline, and how DADL and Code Mode let one governed layer front any MCP server or REST API.
DeepL just rolled out 13 new REST endpoints — style rules, multilingual glossaries, translation memory, /v3/languages, tag_handling v2. The official MCP server has zero of them today. We covered all of them in a 38 KB DADL. Here is the build log.
How to use ToolMesh connectors to populate a fresh NetBox instance from Linode, Hetzner Cloud, Xen Orchestra and other sources — with a trust-building approach from import to autopilot.
AI agents are reaching production faster than governance can keep up. ToolMesh is the missing control layer between AI agents and enterprise systems — governing tool calls and connecting any API in minutes.
Even a stripped-down MCP wrapper is 90 lines of TypeScript. Production wrappers grow past 200. The same integration in DADL takes 40 lines of YAML — and the real gain is not the line count.
Gateways are necessary for secure agent execution, but they do not solve the real scaling problem. The MCP era needs a description layer that makes backend creation trivial.
