ScorpTech x402 Tools

Pythag Check

pythag_check

Read-onlyIdempotent

Check a^2 + b^2 = c^2 for positive integers, with c the hypotenuse. primitive is true when the three sides are coprime. A side triple that fails the equation is rejected. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/pythag-check

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": {
      "a": "<a>",
      "b": "<b>",
      "c": "<c>"
    },
    "name": "pythag_check"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes
`b`	Yes
`c`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety behavior is covered. The description adds meaningful context beyond annotations: rejection of invalid triples, the primitive result condition, payment cost per successful call, and an HTTPS access path.

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 compact and front-loaded: purpose first, then primitive semantics, rejection behavior, and finally pricing/HTTPS access. Every sentence contributes useful information for calling or paying for the tool.

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?

With no output schema, the description does explain the key result behavior: invalid triples are rejected and primitive is true for coprime triples. It does not fully describe the exact success response shape, but for a simple check tool it is nearly complete and annotations cover the operational safety profile.

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, and it does: it defines a, b, and c via the Pythagorean equation, states they are positive integers, and identifies c as the hypotenuse. It does not mention the 1,000,000 upper bound, but the schema already provides that constraint.

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: check whether a^2 + b^2 = c^2 for positive integers with c as hypotenuse. It also defines the primitive result and distinguishes validation from generation, which helps separate it from the sibling pythag_gen.

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 validation wording and the note that failing triples are rejected, but the description does not explicitly say when to use this tool versus pythag_gen or other Pythagorean siblings. It gives enough context to infer its purpose but lacks explicit alternatives or exclusions.

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?