Skip to main content
Glama

Convert units

bursia_unit_convert
Read-onlyIdempotent

Convert units of length, mass, volume, data size or temperature (c, f, k). Pure computation, free.

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": {
      "value": "<value>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "bursia_unit_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget unit, same family as "from".
fromYesSource unit. Length: m km cm mm mi yd ft in. Mass: kg g mg lb oz t. Volume: l ml gal qt cup m3. Data: b kb mb gb tb kib mib gib. Temperature: c f k.
valueYesThe number to convert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"Source unit. Length: m km cm mm mi yd ft in. Mass: kg g mg lb oz t. Volume: l ml gal qt cup m3. Data: b kb mb gb tb kib mib gib. Temperature: c f k."
    • addedInput schema / properties / to / description
      Added value: +"Target unit, same family as \"from\"."
    • addedInput schema / properties / value / description
      Added value: +"The number to convert."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds genuinely new context with 'pure computation, free' – a cost/latency signal not present in any structured field – but says nothing about output shape, precision or error behavior on mismatched families. A 3 is appropriate: some added value beyond annotations, but not rich 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.

Conciseness5/5

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

A single sentence that front-loads the supported unit families and closes with the operational note about cost. There is no filler and nothing an agent must read past to reach the actionable content.

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

Completeness4/5

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

For a three-parameter, purely computational tool with 100% schema coverage, an idempotent/readOnly annotation set and no nested objects, the description covers what the tool does and that it is free. It lacks only the return format (a bare numeric result is implied but unstated since no output schema exists) and mismatch-error behavior.

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

Parameters3/5

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

Schema description coverage is 100%; the `from` property already enumerates every supported unit and the `to` property already states the same-family constraint. The description's parenthetical '(c, f, k)' merely repeats a subset of what the schema documents, so it adds no meaning beyond structured data. Baseline 3.

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?

The description names a specific verb (convert) and resource (units of length, mass, volume, data size, temperature), which is enough to distinguish it from near-siblings such as bursia_color_convert, bursia_case_convert and bursia_timestamp_convert. It stops short of explicitly stating those distinctions, which is why it is a 4 rather than a 5.

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

Usage Guidelines3/5

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

Naming the supported families implicitly tells the agent when the tool applies, and 'pure computation, free' signals that this is a cheap call to prefer freely. However, there is no explicit when-not-to-use guidance, no mention of the requirement that `from` and `to` share a family (arriving only from the schema), and no routing to or from alternative conversion tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources