Skip to main content
Glama

x402-egyptian-fraction

Egyptian Fraction: Egyptian fraction decomposition. 🆓 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-egyptian-fraction"
  }
}

Input Schema

NameRequiredDescriptionDefault
numeratorNo
denominatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / denominator / description
      Removed value: -"Denominator to process"
    • removedInput schema / properties / numerator / description
      Removed value: -"Numerator to process"
  2. Changed2 schema fields changed
    • addedInput schema / properties / denominator
      Added value: +{
      +  "description": "Denominator to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / numerator
      Added value: +{
      +  "description": "Numerator to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

C2.7/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 real behavioral trait: the cost model (5 free trial calls per signed wallet), which tells the agent authentication/payment is involved. Beyond that it says nothing about determinism, error handling for invalid or zero denominators, or result form, leaving significant gaps for a tool with zero annotation coverage.

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?

Two short sentences, front-loaded, with no filler prose. The only inefficiency is the promotional emoji line, which is compact but not about the operation itself.

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

Completeness2/5

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

For a math tool with two fully undocumented parameters, no output schema, and no annotations, the description should specify the input contract and the output form (e.g. a list of unit fractions). It instead leaves both unstated, so an agent cannot confidently construct a correct call from the definition alone.

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?

Both parameters are undocumented in the schema (0% coverage) and the description adds nothing about them. It doesn't say that numerator/denominator must be integer strings, whether they are required (schema says 0 required), or what happens to improper/negative fractions, so an agent must guess the input contract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the operation ("Egyptian fraction decomposition"), but the first clause merely restates the tool name and the second is a near-synonym. It doesn't indicate what the inputs are (a fraction given as numerator/denominator) or what the decomposition produces, so an agent knows the topic but not the shape of the call.

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 versus alternatives (e.g. x402-continued-fraction, x402-decimal-to-fraction, x402-fraction-to-percent), nor any prerequisite guidance beyond the payment note. Usage is only inferable from the tool name.

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