ScorpTech x402 Tools

Unit Convert

unit_convert

Read-onlyIdempotent

Unit conversion across 14 categories with exact defined factors: length, mass, volume (US and imperial), area, speed, time, data (SI kB vs IEC KiB, bits vs bytes), pressure, energy, power, angle, frequency, temperature (C, F, K, Rankine) and fuel economy (mpg US/UK, L/100 km, km/L). Common names and abbreviations accepted; optionally lists the value in every unit of the category. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/unit-convert

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

Input Schema

Name	Required	Description
`to`	No	Target unit (omit with all=true)
`all`	No	Also return the value in every unit of the category
`from`	Yes	Source unit, e.g. mi, kg, F, GiB, psi, mpg
`value`	Yes	Quantity to convert
`precision`	No	Significant digits in the output

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds important behavioral context beyond annotations: exact defined factors, accepted common names/abbreviations, optional all-units output, cost per successful call, x402/Solana payment context, and an HTTPS endpoint.

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 description is front-loaded with the core purpose and structured into category scope, conversion behavior, pricing, and endpoint. It is somewhat dense due to the 14-category list, but the content is purposeful rather than repetitive.

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 5-parameter conversion tool with no output schema, the description covers the important context: category scope, accepted unit names, optional all-units behavior, and payment/endpoint details. It does not fully describe the exact response structure or error behavior, but the core invocation context is sufficient.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds useful meaning: common names and abbreviations are accepted for from/to, categories are enumerated, and all=true returns every unit in the category. Precision is documented only in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: unit conversion across 14 named physical categories. The category list clearly distinguishes it from nearby siblings such as base_convert, color_convert, coord_convert, and timestamp_convert.

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

Usage Guidelines4/5

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

The categories and the optional all=true behavior make the intended use clear: physical-unit conversion, including listing every unit in a category. It does not explicitly name alternatives or when-not-to-use cases, so it stops short of the top score.

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

All ScorpTech x402 Tools 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?