CALCULATE_MCP

convert_units

Convert values between units of length, mass, time, area, volume, speed, data size, and temperature. Provide accurate unit conversions for any specified category and value.

Instructions

Convert common length, mass, time, area, volume, speed, data-size, and temperature units.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>",
      "value": "<value>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "convert_units"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes
`from`	Yes
`value`	Yes
`category`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 14, 2026

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full behavioral burden. It says 'common' units but never states that from/to must belong to the selected category, how incompatible units are rejected, or whether precision/rounding is applied — all important for a conversion tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight, front-loaded sentence with no filler. It is appropriately sized, though its brevity comes at the cost of the details the other dimensions lack.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A four-required-parameter tool with no annotations, no output schema, and no schema descriptions. The description leaves unit-string format, cross-category validation, and result shape entirely unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four required parameters. The description restates the category enum values already present in the schema but adds nothing about the format of 'from'/'to' strings or the meaning of 'value' (base number to convert).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (convert) plus the resource (units) and enumerates the supported measurement categories. This clearly separates it from the calculate_* siblings, though it does not explicitly position itself against list_units or any other tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of the list_units sibling that would help an agent discover valid unit strings. The category list implies scope but not invocation context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server