Skip to main content
Glama

x402-is-kaprekar-number

Is Kaprekar Number: Tests the Kaprekar property where a split of the square sums to the value 🆓 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-kaprekar-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. Changed1 schema field changed
    • addedInput schema / properties / value
      Added value: +{
      +  "description": "Value to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

C2.7/5.0
Behavior2/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 explains the mathematical property but says nothing about the return shape (presumably a boolean), error handling, or how the string parameter is coerced, and there is no output schema to fill that gap. The mention of a 'signed wallet' hints at an auth/billing model but is framed as marketing rather than operational guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first clause is front-loaded and tight, but the trailing '🆓 5 free trial calls per signed wallet' is promotional noise that does not earn its place in a tool definition.

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 trivial single-parameter predicate with no annotations and no output schema, the description is minimally viable: an agent can infer a boolean 'is Kaprekar' result. It nonetheless omits the input contract and the return behavior, which is a real gap given nothing else documents them.

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?

The single parameter has 0% schema description coverage and no type or format documentation beyond 'string'. The description only indirectly implies that 'value' is the number being tested ('sums to the value'), leaving the agent to guess accepted input format and constraints.

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+resource ('Tests the Kaprekar property') and even defines the property (a split of the square sums to the value), so an agent can predict the operation. It does not, however, distinguish itself from the near-identical sibling x402-is-kaprekar, which makes the boundary between the two tools unclear.

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 predicate versus the other 'is-*' number tests, and no note about required input form or error conditions. The only contextual sentence is promotional ('5 free trial calls per signed wallet'), which does not help the agent decide when to invoke 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