ScorpTech x402 API

Digital Root

digital_root

Read-onlyIdempotent

The digital root of a decimal integer. Zero stays zero, and any other magnitude is 1 + (n-1) mod 9, so multiples of 9 have root 9. The sign is ignored. A malformed integer is rejected. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/digital-root

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": {
      "n": "<n>"
    },
    "name": "digital_root"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: exact mathematical behavior, sign ignored, malformed inputs rejected, and a per-successful-call price with an alternate 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 definition and then adds edge-case, error-handling, and pricing details in compact sentences. Pricing and the alternate HTTPS endpoint are secondary but still relevant; overall there is little wasted text.

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 one-parameter math tool with no output schema, the description is nearly complete: it explains the computation, edge cases, invalid-input behavior, cost, and alternate transport. It could state the return type more explicitly, but the formula implies a root value.

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 description coverage is 0%, so the description must carry parameter meaning. It does well by defining n as a decimal integer, explaining sign handling, malformed-input rejection, and the formula using n. It does not mention the 200-digit maximum, but the core semantics are covered.

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 clearly states the specific computation: the digital root of a decimal integer, including the formula and edge-case behavior. It is more precise than a tautology, but it does not explicitly distinguish itself from nearby siblings such as digit_sum or additive_persistence.

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 implied by the well-known operation name and the formula, but the description gives no explicit guidance on when to use this tool versus related sibling tools. It does clarify constraints like zero handling, sign ignoring, and malformed input rejection, which helps an agent decide edge-case behavior.

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

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