ScorpTech x402 Tools

Icbrt

icbrt

Read-onlyIdempotent

The integer cube root of a non-negative decimal integer, the greatest r with r^3 not exceeding n. icbrt(26) is 2 and icbrt(27) is 3. A leading zero is rejected. n has at most 600 digits. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/icbrt

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context beyond annotations: a leading zero is rejected, n has at most 600 digits, pricing ($0.001 USDC per successful call), and an alternative HTTPS endpoint. It does not fully specify error behavior for all invalid inputs, but adds substantial context.

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?

The description is front-loaded with the core definition, followed by examples and constraints. Every sentence adds relevant information: definition, examples, input validation, size limit, pricing, and alternative endpoint. No wasted words.

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 simple one-parameter math tool with no output schema, the description is complete. It covers what the tool computes, input constraints, examples, output implications, pricing, and an alternative access method. An agent has everything needed to call it correctly.

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

Parameters5/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 compensate. It explains that n is a non-negative decimal integer, adds a leading-zero rejection rule not captured by the schema pattern, states the 600-digit limit, and provides concrete examples. This fully clarifies the single parameter's semantics.

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 states a specific verb and resource: 'integer cube root of a non-negative decimal integer' with a precise formal definition and examples. It clearly distinguishes from siblings like isqrt and ipow by specifying cube root vs square root or power.

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 mathematical definition and examples, but there is no explicit guidance on when to use this tool versus alternatives such as isqrt or ipow. The agent can infer the context, but no exclusions or comparisons are 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?