Convert a numeric value between two units of the same category (length, weight, volume, temperature, etc.). Units resolve by id or symbol (e.g. "cm" or "centimeter"). For currency use convert_currency.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Target unit id or symbol. | |
| from | Yes | Source unit id or symbol. | |
| value | Yes | ||
| category | No | Optional category id to disambiguate. |
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?
No annotations are provided, so the description must fully disclose behavioral traits. It states that units resolve by id or symbol and optionally by category, but it does not discuss error behavior (e.g., invalid units), conversion precision, or side effects. This is insufficient for a mutation-like tool.
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 consists of two concise sentences with no redundancy. The first sentence front-loads the verb and resource, and the second sentence provides a key usage guideline.
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 4 parameters, no output schema, and no annotations, the description covers the basic purpose and parameter resolution but omits details like return format, error handling, or valid unit sources. It is adequate for a simple conversion tool but not exhaustive.
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 coverage is 75%, and the description adds that units resolve by id or symbol, which supplements the schema descriptions for 'to' and 'from'. It also explains the 'category' parameter's purpose. However, it does not describe the 'value' parameter beyond the schema's type.
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 explicitly states the verb 'Convert' and the resource 'units of the same category', listing example categories. It also distinguishes itself from the sibling 'convert_currency' by directing currency conversions to that tool.
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 clearly tells the agent when not to use this tool (for currency, use convert_currency) and implies to use for non-currency conversions. However, it does not mention when to use the sibling 'list_units' or other prerequisites.
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: convert_currency handles monetary conversions, convert_units handles other unit conversions, and list_units provides the vocabulary for convert_units. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (convert_currency, convert_units, list_units) in snake_case, making them predictable and easy to understand.
Three tools is exactly right for this domain: one for listing conversions, two for performing conversions (separated by type). No extraneous or missing tools.
The tool set covers the full lifecycle of unit/currency conversion: discover available units (list_units), perform conversions for both monetary and other units. No obvious gaps.