ScorpTech x402 API

Square Obstruction

square_obstruction

Read-onlyIdempotent

Write n = 4^power * odd, with odd not divisible by 4. blocked is true when odd is congruent to 7 mod 8, which is exactly when n is not a sum of three squares. 7 and 28 are blocked. 6 is not. n runs from 0 to 1000000000000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/square-obstruction

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

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond annotations: the valid numeric range and the x402 pricing/HTTPS endpoint details.

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 compact and front-loads the mathematical definition, followed by examples, range, and access/pricing details. The dense first sentence is slightly less immediately readable than a plain-language lead would be, but there is little waste.

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 mathematical predicate with no output schema, the description supplies the defining rule, examples, input range, and access cost. It reasonably implies a boolean blocked result, though it could more explicitly state the return 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 coverage is 0%, so the description must carry parameter meaning, and it does: n is defined via its 4^power * odd decomposition, bounded from 0 to 1000000000000, with worked examples. It does not explain every intermediate term, but it sufficiently characterizes the single input.

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 specific mathematical definition of what the tool computes: whether n is blocked via the 4^power * odd decomposition and congruence 7 mod 8. It is clear enough to distinguish this as a three-squares obstruction test, though it does not explicitly contrast with sibling tools such as three_squares.

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 explains the computation but does not state when to use this tool versus alternatives, nor does it name related sibling tools for three-squares checks. Examples illustrate behavior but not usage selection.

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?