ScorpTech x402 Tools

Isqrt

isqrt

Read-onlyIdempotent

The integer square root of a non-negative decimal integer, the greatest r with r^2 not exceeding n. isqrt(0) is 0 and isqrt(10) 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/isqrt

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Annotations already mark it read-only/idempotent, and the description adds materially new facts: input constraints (leading zero rejected, max 600 digits), cost ($0.001 USDC per successful call via x402 on Solana), and an alternate HTTPS endpoint. Pricing and payment-model disclosure are exactly the kind of behavior an agent cannot infer from annotations or schema.

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?

Front-loaded with the definition and examples, then constraints, then cost and endpoint. Every sentence is functional, though the trailing URL/pricing string makes it slightly denser than the mathematical core requires.

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?

No output schema exists, and the examples (isqrt(10)=3) effectively communicate the return type, so that gap is closed. With input limits and payment terms disclosed, an agent has what it needs to call correctly; only error behavior for out-of-range input is left implicit.

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 the load for the single parameter n. It does: 'non-negative decimal integer', leading-zero rejection, and a 600-digit ceiling, plus examples that convey output format. It stops short of restating the regex pattern, but the meaning is fully 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?

States a precise verb+resource ('integer square root of a non-negative decimal integer') with a formal definition and worked examples (isqrt(0)=0, isqrt(10)=3). It does not distinguish itself from nearby siblings such as icbrt, isquare, or sqrt_cf, but the mathematical definition is unambiguous on its own.

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 never says when to use this tool versus alternatives like icbrt (integer cube root) or isquare, nor does it state preconditions for the caller beyond input validity. The only guidance is implicit in the definition and examples.

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?