Skip to main content
Glama

x420_units_convert

Converts length, mass, area, volume, and temperature between common metric and US units, including roofing squares, and returns a JSON result for each paid call.

Instructions

Unit converter: Converts length, mass, area (incl. roofing squares), volume and temperature between common metric and US units. Pure arithmetic. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.01 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: value, from, to, category, result - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"value":"2400","from":"sqft","to":"square"}.

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": "x420_units_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYestarget unit
fromYessource unit (m, ft, in, mi, kg, lb, m2, sqft, acre, square, l, gal, c, f, k, ...)
valueYesnumber to convert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the material behavior an agent most needs: this is a PAID call ($0.01 USDC per call, settled on Base via x402), the cost is real money drawn from the wallet in X420_MCP_WALLET_PRIVATE_KEY, and the response includes a signed receipt and settlement transaction on top of the computed result. It also characterizes the operation as 'Pure arithmetic,' which usefully implies determinism despite idempotentHint=false (each call costs money). It does not describe error behavior for invalid units or whether the payment is charged on failure.

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?

The definition is a single dense paragraph, correctly front-loaded with purpose, then payment, then return shape, then example. The long disclaimer sentence ('Not professional, legal, insurance, engineering, medical, financial or tax advice') consumes space but is defensible for a paid commercial service. Nothing is genuinely redundant.

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?

With only three required parameters and no output schema, the description supplies the essentials: what it converts, what it costs, what wallet credential is needed, and what the response contains (value, from, to, category, result, receipt, settlement tx). Gaps are minor — no statement on rounding/precision, invalid-unit handling, or whether temperature conversions apply offsets.

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 already 100%, including a unit list in the 'from' field, so the schema carries most of the semantic load and baseline 3 applies. The description adds modest value with a concrete example ({"value":"2400","from":"sqft","to":"square"}) that demonstrates string-typed numeric input and unit aliases such as roofing squares, but it does not explain accepted aliases broadly or case sensitivity.

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 opens with a specific verb+resource ('Unit converter: Converts...') and enumerates the covered categories: length, mass, area (incl. roofing squares), volume, temperature, between metric and US units. This is enough to tell it apart from siblings like x420_currency_convert or x420_time_zone-convert, since currency and time are not in the enumerated domain. It stops short of naming those siblings explicitly, so it earns 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?

Usage is only implied through the enumerated unit categories, which quietly exclude currency and time-zone conversion, and through the sample call. There is no explicit 'use this instead of x420_currency_convert when...' statement and no guidance on what to do for an unsupported unit. The agent must infer the boundary from the word list.

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