ScorpTech x402 API

Sexy Prime

sexy_prime

Read-onlyIdempotent

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

Input Schema

Name	Required	Description	Default
`n`	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?

The annotations already declare the tool as read-only, idempotent, open-world, and non-destructive. The description adds useful non-annotated context: the input range (1 to 1e12), the fixed partner n+6, the price per successful call, and an equivalent 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 core definition is front-loaded and easy to scan. The sentence 'The partner is n+6' is slightly redundant after the opening sentence, and the pricing/HTTPS details add length, but those details are operationally useful rather than filler.

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 boolean predicate with no output schema, the description is nearly complete: it defines the predicate, gives examples, states input bounds, and mentions payment/endpoint details. It could be stronger by explicitly stating that the result is a boolean and by naming the closest sibling alternatives.

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 there is only one parameter and the description meaningfully clarifies it: n is the number to test, n+6 is the partner, and n is bounded from 1 to 1000000000000. It does not restate the integer type, which the schema already provides.

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 a specific mathematical predicate: whether n and n+6 are both prime, with examples (5/11, 7/13) and a counterexample (3/9). It clearly identifies the notion of a sexy prime pair, but it does not explicitly contrast this tool with close siblings such as twin_prime or cousin_prime.

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: call it to test whether n is the smaller member of a prime pair separated by 6. However, there is no explicit guidance about when to use this instead of prime_check, twin_prime, cousin_prime, or next_prime, and no stated 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 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?