ScorpTech x402 Tools

Wilson Prime

wilson_prime

Read-onlyIdempotent

Whether p^2 divides (p-1)! + 1. Inside this cap, 5 and 13 do, and 2, 3, 7, 11, and 17 do not. A composite is rejected. p runs from 2 to 100. This checks the given prime. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/wilson-prime

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

Input Schema

Name	Required	Description	Default
`p`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds useful context beyond annotations: composites are rejected, pricing is $0.001 USDC per successful call via x402, and an HTTPS endpoint is provided.

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 core predicate is front-loaded and the supporting constraints follow in a compact sequence. A few phrases such as “Inside this cap” are slightly awkward, but overall it is efficiently sized and each part contributes useful information.

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 Boolean-style math predicate, the description covers the criterion, valid range, composite rejection, examples, pricing, and endpoint. It could be slightly more explicit that the return is a Boolean, but the “Whether …” framing already implies that.

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: p is bounded to 2–100, composites are rejected, and specific example values are given for true and false cases. It stops short of explicitly saying p must be prime, but the rejection rule and formula make that clear.

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 states the exact mathematical predicate: whether p^2 divides (p-1)! + 1, which clearly identifies a Wilson-prime check. It is specific enough to avoid most confusion, but it does not explicitly name the sibling wilson_quotient or otherwise differentiate itself from related prime tools.

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?

The description gives boundary conditions — p runs from 2 to 100 and composites are rejected — which helps an agent know when a call is valid. However, it does not explicitly say when to use this tool versus alternatives such as wilson_quotient, prime_check, or other prime-related siblings.

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?