ScorpTech x402 API

Wagstaff

wagstaff

Read-onlyIdempotent

The Wagstaff number (2^p + 1)/3 for an odd prime p. p=3 gives 3, p=5 gives 11, and p=7 gives 43. An even number or a composite is rejected. p runs from 3 to 127. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/wagstaff

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": {
      "p": "<p>"
    },
    "name": "wagstaff"
  }
}

Input Schema

Name	Required	Description	Default
`p`	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 idempotency, read-only, and non-destructiveness, so the description's job is smaller. It nonetheless adds real behavioral facts that aren't in annotations: the price ($0.001 USDC, x402 on Solana, only charged on success) and the HTTPS alternative endpoint, so the agent knows a paid path exists.

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?

Formula first, then examples, then validity constraints, then payment/transport info—well front-loaded and no fluff. Slightly dense with pricing and URL details but they earn their place for a paid x402 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?

For a single-param, no-output-schema tool, the description supplies the formula, valid domain, and cost/transport, which is everything needed to call it correctly. Missing is any differentiation from the wagstaff_prime sibling or note on what exactly is returned (the number only vs. primality status).

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 semantic burden, and it does: p must be an odd prime in [3,127], and even or composite inputs are rejected. The min/max range is merely repeated from the schema, but the primality constraint—key to getting a successful call—is only in the description.

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 the exact formula (2^p + 1)/3 for odd prime p and gives worked examples (p=3→3, p=5→11, p=7→43), so the operation is unambiguous. It does not differentiate itself from the sibling wagstaff_prime, which is the main gap.

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 validity conditions (odd prime, 3–127, rejects even/composite) but never says when to use this versus a related sibling such as wagstaff_prime. Cost mention implies a paid call but there is no guidance about alternatives or prerequisites beyond p validity.

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?