Convert between common length units: millimeter, centimeter, meter, kilometer, inch, foot, yard, mile.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Target unit. | |
| from | Yes | Source unit. | |
| value | Yes | Length value to convert. |
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Target unit, echoed back. | |
| from | Yes | Source unit, echoed back. | |
| value | Yes | Input value, echoed back. | |
| result | Yes | Converted value in the target unit. |
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?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Convert' is consistent with a read-only, stateless transform. The description adds no additional behavioral context (e.g., rounding or precision), but none are necessary for this simple operation. It does not contradict the annotations.
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, information-dense sentence that lists all supported units without any fluff. It is front-loaded with the verb and resource, making it easy to parse quickly.
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 simple, stateless nature, a complete input schema, and the presence of an output schema, the description fully covers the tool's purpose and context. No additional information about return values or edge cases is needed.
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 input schema has 100% coverage with clear descriptions for value, from, and to, including enums for the unit fields. The description adds no extra meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.
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 uses the specific verb 'Convert' and specifies the resource ('common length units') along with all eight supported units, clearly distinguishing it from similar converter tools like area-converter or weight-converter. The purpose is immediately obvious.
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 enumeration of length units (millimeter, centimeter, meter, etc.) makes the usage context unambiguous: use this tool for length conversions. However, it does not explicitly name alternative tools or state exclusions, so it earns a 4 rather than a 5.
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.
Most tools have distinct purposes. However, 'hex-to-rgb' is redundant with 'color-converter', which already handles hex-to-RGB conversion, causing potential confusion.
Names follow a consistent lowercase-with-hyphens style, but vary in pattern (e.g., 'angle-converter', 'average-calculator', 'dedup-lines'). One tool ('internal-do-not-call') deviates from the descriptive norm.
With 46 tools, the server is heavily populated. Many converters could be merged into a generic unit converter, and there is redundancy, making the surface unnecessarily large for a single server.
The server covers a broad range of utility domains: converters, text processing, math, cryptography, etc. Minor redundancies exist (e.g., hex-to-rgb vs color-converter), but the set is otherwise comprehensive.
