Skip to main content
Glama

x402-is-sophie-germain

Is Sophie Germain: Checks whether value is a prime p for which 2p+1 is also prime, 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-sophie-germain"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / value / description
      Removed value: -"Value to process"
  2. Changed1 schema field changed
    • addedInput schema / properties / value
      Added value: +{
      +  "description": "Value to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose the return type ('returning a boolean') and the payment model ('5 free trial calls per signed wallet'), which are genuinely useful. However it says nothing about behavior on non-numeric, negative, fractional, or very large inputs — a real gap for a primality tool taking an untyped string.

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?

Front-loaded with the definition and return type in one sentence; the trial-call note is tacked on with an emoji but is short. No redundant sentences, though the promotional tail is not strictly tool-selection information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 1-param, boolean-returning tool with no annotations or output schema, the definition plus return type covers the core. It falls short on input format and edge-case behavior, which an agent would need to call it correctly on ambiguous string input.

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 the single parameter 'value' is typed as a string with no description. The description partially compensates by identifying value as the prime p being tested, but gives no format, range, or integer-only constraint, which matters because the schema says string.

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 gives a precise mathematical definition — 'a prime p for which 2p+1 is also prime' — plus the return type (boolean). This defines the operation specifically enough to distinguish it from the many nearby siblings (x402-is-safe-prime, x402-is-prime, x402-is-twin-prime) without needing to name them.

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 guidance on when to use this versus x402-is-prime, x402-is-safe-prime, or x402-is-twin-prime, and no mention of prerequisites or input constraints. The math definition implies the use case but the description never states it.

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