Report a bug, missing conversion, or quality issue to the ConvertFileFast team.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | No | Tool or conversion involved, e.g. 'convert_file pdf-to-docx'. | |
| context | No | Extra detail: error message, input format, expected vs actual. | |
| summary | Yes | Short description of what went wrong or what is missing. | |
| category | No | Feedback category. | other |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description indicates the side effect of sending feedback, consistent with idempotentHint false. However, it does not explain what happens after reporting (e.g., confirmation, response) or elaborate on the openWorldHint annotation. The output schema may cover return values, but the description could add behavioral context.
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 a single sentence with no wasted words. It is front-loaded with the purpose and immediately actionable. Perfect conciseness.
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?
For a simple feedback tool with full schema coverage and an output schema, the description is mostly complete. It lacks usage guidelines and behavioral details, but these are minor gaps given the tool's straightforward nature. Slight improvement possible.
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?
Schema description coverage is 100%, so the schema already documents all parameters. The description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the description does not degrade but adds no value.
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 the verb 'Report' and the resource: bugs, missing conversions, or quality issues to the ConvertFileFast team. It distinguishes from sibling tools that focus on file operations, making the purpose specific and unambiguous.
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?
While not explicitly stating when to use this tool vs alternatives, the sibling context (all file processing tools) makes it obvious that this is for reporting issues. A clear when-not statement is missing but not critical given the clear domain separation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose, covering different file operations (compress, convert, extract, merge, split, etc.) and billing management. No two tools overlap in functionality.
Most tool names follow a verb_noun pattern (compress_image, protect_pdf), but a few deviate (images_to_pdf, list_supported_conversions) causing minor inconsistency. The pattern is largely predictable.
17 tools is slightly above the typical well-scoped range, but still reasonable given the breadth of file manipulation and billing operations. Each tool serves a distinct need.
The file conversion and PDF manipulation operations are well-covered (compress, convert, extract, merge, split, protect, etc.). The billing tools are complete for subscription and credit management. Minor gaps exist, such as batch operations or image format conversions.