ScorpTech x402 Tools

Beatty Sqrt2

beatty_sqrt2

Read-onlyIdempotent

floor(n*sqrt(2)). n=1 gives 1, n=2 gives 2, n=3 gives 4, n=5 gives 7, and n=10 gives 14. n runs from 1 to 1000000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/beatty-sqrt2

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/destructive safety, but the description adds valuable context annotations cannot: a per-call price ($0.001 USDC via x402 on Solana) and an equivalent HTTPS endpoint. It also caps the domain at n=1,000,000, though it does not say what happens when n exceeds it. The openWorldHint=true annotation is somewhat questionable for a deterministic math function, but the description does not contradict it.

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 definition is front-loaded, the five examples each disambiguate floor behavior at a boundary (e.g., n=3 → 4), and the range, price, and alternate endpoint follow in a tight sequence with no 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 one-parameter tool with no output schema, the description supplies both the formula and sample returned values, so an agent knows the return shape. Remaining gaps are edge behavior: out-of-range n, payment failure handling, and response format beyond the examples.

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 0%, so the description must carry the burden, and it does reasonably: the formula establishes that n is the index, the examples map inputs to outputs, and the 1-to-1,000,000 range is restated. It still never states that n must be an integer, which the schema enforces but does not describe.

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 gives a precise mathematical definition (floor(n*sqrt(2))) plus worked examples, so the operation is unambiguous. However, it never distinguishes this from close siblings like `beatty` or `beatty_sqrt2_comp`, which an agent must infer from names alone.

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?

There is no statement of when to use this tool versus the `beatty` or `beatty_sqrt2_comp` siblings, nor any exclusion criteria. The only usage-relevant information is the payment prerequisite, which is behavioral rather than routing guidance.

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?