Skip to main content
Glama

number-to-words

Number and cheque-amount words: English (US, UK, Indian lakh/crore) — Spells out a number or a money amount in English words for a cheque, contract or invoice, for an agent that must write the amount in words next to the figures. Locales: en-US ("one hundred twenty-three"), en-GB ("one hundred and twenty-three"), en-IN (lakh and crore, "one crore twenty lakh"). With a currency it returns the integer words, the minor-unit fraction as digits over 10^exponent ("56/100"

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": {
      "items": "<items>"
    },
    "name": "number-to-words"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose non-obvious output behavior: with a currency it returns integer words plus the minor-unit fraction rendered as digits over 10^exponent ("56/100"). It omits batch semantics (the schema accepts 1-100 items), negative-amount handling, and failure behavior.

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-loaded and dense with useful specifics rather than filler; the locale list and the fraction example each earn their place. The trailing parenthetical is truncated mid-example ("56/100" with an unbalanced quote), which slightly hurts readability.

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?

Covers the core semantics (locales, currency, exponent override) well for a computation tool with no annotations or output schema, but leaves notable gaps: the batch/array input shape, handling of negative amounts allowed by the pattern, and what happens for unsupported locale or currency values.

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?

Top-level schema coverage is 0% (the required `items` array is undocumented), and the description compensates by enumerating the locale values with example outputs (en-US, en-GB, en-IN lakh/crore) and explaining what `currency`/`exponent` change in the result. It does not clarify that input is an array of up to 100 line items rather than a single scalar.

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 ("Spells out a number or a money amount in English words") and names the concrete artifacts it serves (cheque, contract, invoice), which separates it from numeric siblings such as locale-number or cash-rounding.

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 when-to-use context: an agent that must write an amount in words next to figures on a cheque, contract or invoice. It does not name an explicit alternative or state when not to use it, so it stops short of full routing 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