text_numbers
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) up to 10^36, or English number words ("two hundred and fifty-first") parsed back to a numb...
This record as markdown: /tools/dev-tanod-tanod/text-numbers.md
What text_numbers does on Tanod
AI agents call text_numbers to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | to_words (default: `value` to English words) or to_number (`text` to a number). |
text | object | — | to_number: English number words. |
style | string | — | to_words style: cardinal (default), ordinal, currency or year (an integer 1-9999). |
value | object | — | to_words: a decimal string or an integer (no floats: no rounding surprises). |
currency | string | — | style=currency: AUD, BRL, CAD, CHF, CNY, EUR, GBP, INR, JPY, MXN, PHP, SGD or USD (default). |
Parameters from the server's own tool schema.
Why text_numbers is rated Low
Even though text_numbers only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs text_numbers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For text_numbers, this is the rule to start with:
text_numbers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every text_numbers call is checked against it from then on.
Questions about text_numbers
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) 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. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
text_numbers accepts 5 parameters: mode, text, style, value, currency. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for text_numbers: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Tanod. Nothing to install.
text_numbers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the text_numbers rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for text_numbers. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
text_numbers is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue