Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-number-to-words

Number To Words: Convert number to words. 🆓 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-number-to-words"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / n / description
      Removed value: -"N to process"
    • removedInput schema / properties / value / description
      Removed value: -"Value to process"
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden, but it only reveals a free-trial quota of 5 calls per signed wallet. It says nothing about handling of negatives, decimals, very large numbers, locale/language output, or the response format — all material for a conversion tool.

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?

Very short and front-loaded; the tool name is restated in the first clause, which is redundant but costs little. The trial-call note is compact and informational rather than padding.

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 tool with two unexplained parameters, no output schema, and no annotations, the description is far too thin — an agent cannot tell what to pass in or what comes back. The only compensating detail is the pricing/quota note.

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 description coverage is 0% across two parameters named 'n' and 'value', neither of which is required. The description's mention of 'number' gives only a hint that one of them is the input, and it never explains why two synonymous parameters exist or which takes precedence.

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?

States a specific verb and resource: 'Convert number to words', which is unambiguous about the transformation performed. It does not distinguish itself from near-siblings like x402-number-humanize, x402-to-ordinal, or x402-format-roman-num, so an agent choosing among numeric-formatting tools gets no routing help.

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?

No when-to-use or when-not-to-use guidance is offered, and no alternative tool is named. The only extra sentence is a pricing/trial note, which does not help select this tool over the many other number-formatting siblings.

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.