MoneyTools x402 agent toolkit

Unit converter

unit_convert

Read-onlyIdempotent

Length, mass, volume, area (incl. 坪/ping), speed, time, data (KB vs KiB), energy, pressure, temperature and exact wei/gwei/ETH conversion. Free: 10 calls/day; then $0.001/call via x402 (MCP params._meta["x402/payment"] or HTTP) or X-API-Key credits. [served by tools.moneytools.dev]

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

Input Schema

Name	Required	Description
`to`	Yes	unit
`from`	Yes	unit
`value`	Yes	number

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and openWorld semantics, and the description goes beyond them by disclosing quota (10 free calls/day), pricing ($0.001/call), and the two payment mechanisms (x402 via _meta or HTTP, and X-API-Key credits) plus the serving host. That is genuinely decision-relevant context an agent cannot get from annotations. It does not cover behavior on invalid or unsupported units.

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?

Two dense sentences; capability list first, commercial terms second, with the host tag appended. The pricing sentence is long but every clause (free tier, per-call price, two payment paths) affects whether an agent should call it, so it earns its place.

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?

An output schema exists, so return values need not be explained, and the three required params are fully covered by the schema. The description supplies the remaining agent-critical facts: supported domains, exactness for crypto, cost model and payment channel.

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%, so value/from/to are already documented, though only with terse 'number'/'unit' labels and no enum. The description adds a useful hint that units include crypto (wei/gwei/ETH) and binary-vs-decimal data units, but offers no format or case rules for the unit strings.

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 enumerates the exact conversion domains covered (length, mass, volume, area including 坪/ping, speed, time, data KB vs KiB, energy, pressure, temperature, and wei/gwei/ETH), which is a precise resource statement, and the crypto detail ('exact wei/gwei/ETH') hints at its differentiator. It stops short of naming a sibling to contrast with (e.g. time_convert, currency_convert), so differentiation is inferred rather than stated.

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?

The description lists what it converts but never says when to choose it over the overlapping siblings such as time_convert or currency_convert, nor does it state prerequisites or exclusions. The only 'when' guidance is billing related, not selection related.

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

All MoneyTools x402 agent toolkit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?