Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-is-achilles-number

Is Achilles Number: Checks whether an integer is at least two, powerful and not a perfect power 🆓 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-achilles-number"
  }
}

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/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 does disclose a real behavioral trait beyond structured data – the pricing/limit signal '🆓 5 free trial calls per signed wallet' – which tells the agent about cost and quota. It says nothing about output format (boolean?), handling of non-integer or negative input, or error behavior.

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?

Compact and front-loaded: the predicate definition comes first, then the pricing note. No redundant sentences, though the 'Is Achilles Number:' prefix is a redundant restatement of the tool name.

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?

With no annotations and no output schema, the description must convey more than it does. The purpose is fully covered for a boolean math predicate, but the input contract (string integer, optionality) and the return shape remain undefined, leaving an agent to guess at invocation details.

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

Parameters2/5

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

Schema coverage is 0%: the single 'value' parameter is typed only as a string with no description, and it is not even marked required. The description implies the input is an integer but does not clarify whether it must be passed as a decimal string, whether large values are accepted, or what happens for non-numeric strings, so it fails to compensate for the coverage gap.

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 gives a specific verb and resource ('Checks whether an integer is...') and defines the mathematical predicate ('at least two, powerful and not a perfect power'), which distinguishes it from the neighboring x402-is-powerful and x402-is-perfect tools. It does not, however, name those siblings explicitly, so an agent must infer the distinction from the definition alone.

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 statement of when to use this tool versus the many closely related predicate tools (x402-is-powerful, x402-is-perfect, x402-is-achilles), nor any prerequisites or input-format guidance. The definition of the number doubles as implicit scope, but no explicit usage routing is offered.

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.