The same specification, compiled two ways
One OpenAPI document converted twice: one tool per operation, and the surface a compiler designs from the same bytes. Pick any operation to see the rename, the withheld arguments, the rationale the planner recorded, and the governance the tool has to satisfy before it can run.
Sources: Governed MCP Tool Surfaces · api-mcp-compiler
Instrument / Agent tool surfaces
One document, two tool surfaces
One document, two conversions. On the left, one tool per operation, which is what a converter emits. On the right, the surface the compiler designs from the same bytes. Pick any operation to see what changed, the rationale the planner recorded, and what the governance manifest says before the tool is allowed to run.
One tool per operation transliterated
Compiled surface designed
Where these numbers come from
Every value in this instrument is output from an actual compiler run, not an illustration. Each pane is generate over the same example specification shipped in the repository, once with --planner baseline and once with --planner semantic. The rationales and confidences are the planner's own decision records from plan, and the governance block is the manifest from policy. The specifications are small on purpose: they are the fixtures, and they make the transformation legible in a way a 400-operation estate would not.
Nothing here calls a network. The data is compiled into the page.