Skip to main content
Glama

Text Analysis & Cleanup Tools (Tanod)

text_numbers

Read-onlyIdempotent

utilpeek: Convert numbers to English words. For units use convert_units. Returns a number spelled out in English (cardinal, ordinal, year, or currency for 13 currencies, rounded half-even to the minor unit; INR in lakh and crore by default) up to 10^36, or English number words ("two hundred and fifty-first") parsed back to a number. value is a decimal string or an integer, never a float. Invalid or out-of-range input is a 422 (not charged). Typically under 0.3 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day.

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": "text_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoto_words (default: `value` to English words) or to_number (`text` to a number).to_words
onlyNostyle=currency: end with "only" (default false).
textNoto_number: English number words.
styleNoto_words style: cardinal (default), ordinal, currency or year (an integer 1-9999).cardinal
valueNoto_words: a decimal string or an integer (no floats: no rounding surprises).
currencyNostyle=currency: AUD, BRL, CAD, CHF, CNY, EUR, GBP, INR, JPY, MXN, PHP, SGD or USD (default).USD
lakh_croreNostyle=currency: Indian lakh and crore words (default: INR only).

Output Schema

NameRequiredDescriptionDefault
textNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
styleNo
valueNo
wordsNo
numberNo
sourceNo
currencyNo
rounded_toNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / properties / currency / title
      Removed value: -"Currency"
    • removedInput schema / properties / lakh_crore / default
      Removed value: -null
    • removedInput schema / properties / lakh_crore / title
      Removed value: -"Lakh Crore"
    • removedInput schema / properties / mode / title
      Removed value: -"Mode"
    • removedInput schema / properties / only / default
      Removed value: -null
    • removedInput schema / properties / only / title
      Removed value: -"Only"
    • removedInput schema / properties / style / title
      Removed value: -"Style"
    • removedInput schema / properties / text / default
      Removed value: -null
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / properties / value / default
      Removed value: -null
    • removedInput schema / properties / value / title
      Removed value: -"Value"
    • removedInput schema / title
      Removed value: -"text_numbersArguments"
  2. Changed2 schema fields changed
    • addedInput schema / properties / lakh_crore
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "style=currency: Indian lakh and crore words (default: INR only).",
      +  "title": "Lakh Crore"
      +}
    • addedInput schema / properties / only
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "style=currency: end with \"only\" (default false).",
      +  "title": "Only"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / currency / description
      Added value: +"style=currency: AUD, BRL, CAD, CHF, CNY, EUR, GBP, INR, JPY, MXN, PHP, SGD or USD (default)."
    • addedInput schema / properties / mode / description
      Added value: +"to_words (default: `value` to English words) or to_number (`text` to a number)."
    • addedInput schema / properties / style / description
      Added value: +"to_words style: cardinal (default), ordinal, currency or year (an integer 1-9999)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "currency": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "number": {},
      +    "rounded_to": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "style": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "text": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "value": {
      +      "type": [
      +        "string",
      +        "integer",
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "words": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value: 422 on invalid/out-of-range input with no charge, half-even rounding to the minor unit, 10^36 ceiling, INR lakh/crore default, latency, price, and free-tier quota. It does not describe the response shape, but an output schema exists.

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 with the core action and the sibling exclusion, then pricing and limits. It is dense and packs many clauses into one paragraph, but nearly every clause carries operational information; only the pricing/quota tail is arguably secondary.

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

Completeness5/5

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

For a 7-parameter, 0-required tool with full schema coverage and an output schema, the description covers direction, constraints, rounding, range, errors, and cost. Nothing an agent needs to invoke it correctly is missing.

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%, so baseline is 3. The description adds meaning beyond the schema: `value` must be a decimal string or integer and never a float, currency covers 13 codes, and lakh_crore defaults to INR only. These clarify intent rather than merely restating field descriptions.

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 ('Convert numbers to English words') and covers both directions (to_words and to_number). It explicitly distinguishes itself from the sibling convert_units, so an agent can route correctly without opening the schema.

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?

Explicitly routes unit conversion to convert_units and explains the mode split (to_words vs to_number). It does not enumerate when-not conditions beyond that, but the primary alternative is named clearly.

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.