Retrieve full native schemas and a source example for DrawFather diagram formats. Use when concise capability discovery is insufficient for building or validating JSON input.
Explicitly retrieve full native schemas and a source example. For concise discovery prefer get_capabilities.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the material behavioral fact that this returns expanded schemas plus a concrete source example, which tells the agent about payload weight versus get_capabilities.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with no filler, and the primary action is front-loaded ahead of the alternative-routing clause.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters and no output schema, the description bears the burden of describing the return, and it does so at a high level (full native schemas + source example). It stops short of noting scale or structure, but nothing essential for correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is no schema semantics to clarify; the default baseline of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: retrieving full native schemas plus a source example. It also distinguishes itself from the sibling get_capabilities, though the ambiguous name 'get_format' (format of what?) leaves the resource slightly under-specified.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: use get_capabilities for concise discovery, and this tool when you need the full/explicit schema plus an example. Clear selection context, though it doesn't state what happens if no format exists or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.