ScorpTech x402 Tools

Base Convert

base_convert

Read-onlyIdempotent

Convert an integer from one base to another. Bases run from 2 to 36, and letters may be any case. A digit that is not valid in the source base is rejected. The result is the digit string in the target base. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/base-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>",
      "to": "<to>"
    },
    "name": "base_convert"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes
`from`	Yes
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/destructive/openWorld, but the description adds useful behavior: invalid digits in the source base are rejected, letters may be any case, and the output is a digit string in the target base. It also discloses the payment model and HTTPS endpoint, though it does not describe error response format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the core purpose, followed by input constraints, output format, and payment details. No filler; every sentence contributes useful context for invoking the tool.

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 simple base-conversion tool with annotations covering safety and no output schema, the description gives enough: input base range, value validity, output format, and payment context. Negative number handling and error response shape are unmentioned, but these are minor for this tool.

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 0%, so the description must carry the burden. It partially compensates by explaining the 2–36 base range (for from/to), case-insensitive letters, and rejection of invalid source digits (for value), plus the output meaning. It does not explicitly map parameter names, mention negative values, or note the maxLength constraint.

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?

States a specific verb ("Convert") and resource ("an integer from one base to another") and narrows scope to bases 2–36. Among the many sibling conversion tools (unit_convert, color_convert, format_convert), this clearly identifies base conversion as its job.

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 use case is implied by the description: convert an integer between bases. It does not explicitly state when to choose this tool over alternatives or mention any sibling tool, so guidance remains inferred rather than stated.

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?