Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Number to words, in English: write a number out in English words

number_words
Read-only

Write a whole number (up to trillions, negatives allowed) out in English words, e.g. for cheques and invoices. Also returns the cheque form with 'and' cents when given a decimal amount. Use when amounts must be written out in full. Example: number=1234.5. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "number": "<number>"
    },
    "name": "number_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesThe number, decimals allowed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/destructive/openWorld, so the bar is lower; the description adds real value by disclosing cost ($0.01/call via x402 or card key), 25 free calls, that failed calls are free, and that repeats are not free — which explains the idempotentHint=false despite being a pure computation. It also notes the extra cheque-form output for decimals, which annotations never convey.

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?

Front-loads the core operation and scope in the first sentence, then examples, then pricing. Structure is good, though the pricing/clause chain at the end is dense and slightly long relative to the tool's simplicity.

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

Completeness4/5

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

No output schema exists, and the description compensates by describing both return shapes (English words, plus cheque form with 'and' cents for decimals). Cost and failure-pricing behavior round out what an agent needs to call it responsibly; only exact output formatting is left implicit.

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 100% and there is a single parameter, so baseline is 3; the description still adds meaning by stating the accepted range (up to trillions), that negatives are allowed, and specifically what a decimal value produces (cheque form with 'and' cents) — behavior the schema's 'decimals allowed' does not explain.

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

Purpose5/5

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

States a specific verb and resource ('write a whole number ... out in English words') with scope limits (up to trillions, negatives allowed) and a concrete example (number=1234.5). An agent can immediately distinguish this from sibling converters such as number_roman.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context ('for cheques and invoices', 'Use when amounts must be written out in full') plus a worked example. It does not name a when-not condition or an explicit alternative, but the intended use is unambiguous.

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.