Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-goldbach-pairs

Goldbach Pairs: Lists every pair of primes that sum to a given even integer and returns an empty list for odd input 🆓 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-goldbach-pairs"
  }
}

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. 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 carries the full burden and it does disclose one genuinely useful behavior: odd input returns an empty list rather than erroring. It also surfaces the paywall (5 free trial calls per signed wallet). However it omits input constraints (must be even, magnitude limits), output structure, and behavior for negative/zero or very large inputs.

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?

One tight sentence with the core definition front-loaded; the pricing tag is appended boilerplate but small. No wasted prose, though the emoji/paywall fragment is not strictly part of the tool's contract.

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 single-parameter deterministic math utility the purpose and edge case are covered, and no output schema exists so return shape is unaddressed by design. Still, an agent lacks input format/range guidance and any note on error versus empty-result semantics for invalid 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 sole parameter is typed only as "string", so the description must compensate. It adds the key semantic that the value is an even integer, but does not reconcile the string type or specify format/range (e.g. decimal string, bounds), leaving the agent to guess how to encode the input.

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?

States a specific verb (lists) and resource (every pair of primes summing to a given even integer), and adds the defining edge case (odd input yields an empty list). An agent can distinguish this from siblings like x402-prime-factors or x402-is-twin-prime-pair without opening a schema.

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 or when-not-to-use guidance and no named alternative. The odd-input note is a behavioral fact, not usage routing, so the agent must infer that this tool exists solely to evaluate Goldbach decompositions.

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.