Skip to main content
Glama

x402-is-twin-prime-pair

Is Twin Prime Pair: Checks that a and b are both prime and differ by exactly 2, returning a boolean 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-is-twin-prime-pair"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNo
bNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / a / description
      Removed value: -"A to process"
    • removedInput schema / properties / b / description
      Removed value: -"B to process"
  2. Changed2 schema fields changed
    • addedInput schema / properties / a
      Added value: +{
      +  "description": "A to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / b
      Added value: +{
      +  "description": "B to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return type (boolean) in the absence of an output schema, and it notes the pricing model (5 free trial calls per signed wallet). It does not say what happens with non-numeric or negative input, nor whether the two arguments must be ordered, so the behavioral picture is only partial.

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 semantic content is front-loaded in a single tight sentence, with the return value included. The trailing free-trial marketing string is noise but small. Almost every token earns its 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 boolean predicate with no output schema and no annotations, the description covers what is checked and what is returned. The remaining gap is input validation behavior and the string-typed arguments, which is minor for a tool this narrow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and neither parameter is documented in the schema, so the description must compensate. It does explain the relationship between a and b (both prime, differ by 2), which gives real meaning beyond the bare names. It does not mention that the schema types them as strings nor what numeric format is expected, leaving the actual input contract unclear.

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 a specific verb and resource with exact semantics: checks that a and b are both prime and differ by exactly 2, returning a boolean. An agent can tell this apart from the general x402-is-prime at a glance. It does not, however, distinguish itself from its near-identical siblings x402-is-twin-prime and x402-is-prime-pair, which is where the ambiguity actually lies.

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?

There is no when-to-use / when-not-to-use guidance and no mention of the closely related siblings (x402-is-twin-prime, x402-is-prime-pair, x402-is-prime). Usage is only implied by the predicate semantics. An agent gets no help choosing among the many overlapping primality tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources