list_conversionsList all supported file conversion routes. Filter by source format to see target formats available for conversion.
List all supported conversion routes. Optionally filter by source format to see what you can convert FROM a specific format.
| Name | Required | Description | Default |
|---|---|---|---|
| source_format | No | Filter by source format (e.g. "docx" returns all DOCX target options) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare 'readOnlyHint: true' and 'openWorldHint: false'. The description adds that the tool lists 'all' conversions, implying completeness within a bounded set, but does not provide significant behavioral context beyond what annotations convey.
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?
The description is two sentences long, front-loaded with the core purpose, and contains no extraneous information. Every sentence earns its place.
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?
Given the tool's simplicity (one optional parameter, no output schema), the description sufficiently conveys its functionality and the filtering option. Annotations complement the behavioral profile, making the definition complete.
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?
With 100% schema description coverage, the baseline is 3. The description adds value by providing an example ('e.g., "docx" returns all DOCX target options'), which helps the agent understand the filtering behavior beyond the schema statement.
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?
The description clearly states 'List all supported conversion routes,' using a specific verb and resource. It distinguishes the tool from sibling tools like 'convert_file' and 'compress_file' by focusing on listing rather than performing actions.
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?
The description implicitly indicates when to use the tool (to see available conversions) and suggests filtering by source format. However, it does not explicitly state when not to use it or mention alternatives like 'convert_file' for performing conversions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.