Skip to main content
Glama

units_convert

Read-onlyIdempotent

Convert dimensionally compatible scientific units while retaining the original expression, including symbols such as ų.

Instructions

Convert dimensionally compatible scientific units, retaining the original expression (including ų).

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>",
      "unit": "<unit>",
      "target": "<target>"
    },
    "name": "units_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description contributes one genuine behavioral detail — that the original expression is retained, including unicode exponents like ų — but says nothing about error handling for incompatible units or rounding/precision behavior.

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?

A single sentence with no filler, and the core action is front-loaded before the parenthetical caveat. The trailing "(including ų)" is slightly cryptic but does carry information.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the operation is conceptually simple. However, with all three parameters undocumented at 0% schema coverage and no guidance on unit-string syntax or incompatible-unit behavior, the definition is thinner than the schema warrants.

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%, so the description must carry all parameter meaning, and it does not. The three parameters (value, unit, target) are never named or explained; the only hint is "including ų," which suggests unicode unit strings but gives no format rules or examples.

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 states a specific verb ("convert") plus resource ("scientific units") and adds a scoping constraint ("dimensionally compatible"). It is instantly distinguishable from the sibling tools, none of which deal with units, though it stops short of a full scope statement (e.g., supported unit systems).

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?

The phrase "dimensionally compatible" implies a precondition for use, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage is inferable but not spelled out.

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