Skip to main content
Glama

x402-percentage-of

Percentage Of: Computes part divided by whole, times 100, as a percentage 🆓 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-percentage-of"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNo
wholeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / part / description
      Removed value: -"Part to process"
    • removedInput schema / properties / whole / description
      Removed value: -"Whole to process"
  2. Changed2 schema fields changed
    • addedInput schema / properties / part
      Added value: +{
      +  "description": "Part to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / whole
      Added value: +{
      +  "description": "Whole to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.3/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 behavioral burden. It does disclose the access/payment model ('5 free trial calls per signed wallet'), which is useful context an agent cannot get from the schema, but it says nothing about what happens after the free calls, latency, or error behavior for invalid input.

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?

The definition is a single tight clause with the core computation front-loaded, plus one short access note. The emoji and promotional tail add noise but cost little in length.

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 simple two-input math tool with no output schema, the description covers the operation and the payment model but omits the return format (e.g., whether the result is a number or a formatted string) and input format expectations. Adequate but with visible gaps for a tool whose schema is entirely undocumented.

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

Parameters4/5

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

Schema coverage is 0% and neither 'part' nor 'whole' is documented in the schema, so the description's 'part divided by whole' is the only thing that tells the agent which value is the numerator and which is the denominator. It stops short of specifying accepted formats (raw number vs. percent string) despite both parameters being typed as strings.

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 precise verb-and-resource definition — 'Computes part divided by whole, times 100, as a percentage' — so an agent knows exactly what arithmetic is performed. It does not, however, distinguish itself from near-identical siblings such as x402-percent-of, x402-percent-of-value, or x402-proportion-of, which appear to do the same thing.

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 pick this tool over x402-percent-of, x402-percent-of-value, x402-ratio-of, or x402-fraction-to-percent. The only extra guidance is the promotional '5 free trial calls per signed wallet' line, which is billing information, not selection guidance.

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