ScorpTech x402 API

Cousin Prime

cousin_prime

Read-onlyIdempotent

Whether n and n+4 are both prime. 3 pairs with 7, and 7 pairs with 11. 5 does not pair with 9. n runs from 1 to 1000000000000. The partner is n+4. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/cousin-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": {
      "n": "<n>"
    },
    "name": "cousin_prime"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, non-destructive, and open-world. The description adds important behavioral context beyond the annotations: the valid n range and the $0.001 USDC x402 payment model per successful call, plus an HTTPS endpoint.

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 definition is front-loaded with the core predicate and remains appropriately short. Some content is redundant, especially restating “The partner is n+4” after the first sentence and examples, but the pricing and endpoint details earn their place.

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 simple one-parameter mathematical predicate, the description supplies the operation, range, examples, payment model, and alternate HTTPS endpoint. Because no output schema exists, it could more explicitly state that the return value is boolean, but “Whether ...” strongly implies that behavior.

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%, but the single parameter n is constrained by minimum/maximum in the schema. The description compensates by explaining that n is the smaller member of the pair, that the partner is n+4, and by giving concrete examples, though it does not document the response value.

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 precise mathematical predicate: whether n and n+4 are both prime. It distinguishes the operation through the n+4 partner relation and examples (3 with 7, 7 with 11, 5 not with 9), so an agent can identify it as cousin-prime checking rather than twin-prime or generic primality testing.

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 definition: an agent can infer this is the tool for checking cousin-prime pairs where the difference is 4. However, it does not explicitly mention when to use alternatives such as twin_prime or sexy_prime, nor does it state when not to use this tool.

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?