Skip to main content
Glama

X420 agent services

x420_units_convert

Read-onlyIdempotent

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. Price: $0.01 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: value, from, to, category, result.

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 observed

TDQS

A3.8/5.0
Behavior4/5

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

The description discloses a major non-obvious trait: the hosted tool does not pay and does not return the deliverable, only payment instructions (pay_to, network, price, x402 URL). It also states the price and network, and gives the exact paid-deliverable shape. Annotations already cover read-only/idempotent/non-destructive, and nothing conflicts; the only gap is that it does not describe error behavior or what invalid units produce.

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 purpose is front-loaded in the first sentence, followed by the critical payment-flow constraint before the legal disclaimer. The blanket 'not professional, legal, insurance, engineering, medical, financial or tax advice' line adds little for an arithmetic converter and could be trimmed, but the remainder is dense and useful.

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

Completeness5/5

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

For a paid x402 tool with no output schema, the description covers the arithmetic scope, the payment handshake, the pricing, the alternative local-server path, and the paid deliverable's JSON fields. An agent has everything needed to invoke it and interpret the response.

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 coverage is 100%, with the schema itself giving example units for 'from' (m, ft, in, mi, kg, lb, m2, sqft, acre, square, l, gal, c, f, k) and descriptions for all three parameters. The description adds category-level context but no format or validation details beyond the schema, so the baseline of 3 applies.

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 and resource ('Unit converter: Converts length, mass, area (incl. roofing squares), volume and temperature') and enumerates the covered unit categories, which implicitly separates it from currency and time-zone converters. It does not explicitly name those siblings, so differentiation is by scope rather than by direct reference.

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?

There is clear procedural guidance for obtaining a result ('GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE' or run the local server with your own wallet key). However, there is no explicit statement of when to choose this tool over x420_currency_convert or x420_time_zone-convert, nor any exclusion beyond the implied physical-unit scope.

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