Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

math_number_to_words

Read-onlyIdempotent

Spell any integer into English or Spanish words up to 10^36. Ideal for rendering numbers as text on cheques, legal documents, or accessibility.

Instructions

Integer to English or Spanish Words. Spell a whole number out in words: English (short scale, where 10^9 is a billion) or Spanish (long scale, where 10^12 is a billon), up to magnitudes below 10^36. Accepts negatives and BigInt-safe integer strings beyond the JS-safe range. Use this to render a number as spoken or cardinal text (cheques, legal copy, accessibility); use conversion_string_number for free-form numeric format conversion, or math_roman_numerals_converter for Roman numerals. Runs locally: read-only, non-destructive, contacts no external service, rate-limited (60 requests/minute for anonymous callers). Returns the normalized integer plus its words.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesInteger to spell out, as a digits-only string (optional leading minus) or a whole number. Use a string for values beyond JS-safe integer range. Magnitude must be below 10^36; non-integers and floats are rejected.
languageNoOutput language: en for English short scale, es for Spanish long scale. Defaults to en.en

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the conversion succeeded.
resultNoThe converted number and its word form.
Behavior5/5

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

Beyond the annotations (readOnlyHint, destructiveHint, idempotentHint), the description adds critical behavioral details: local execution, no external service calls, rate limiting (60 req/min for anonymous), and the return value structure (normalized integer plus words). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact at 4 sentences, front-loading the core purpose. Each sentence serves a distinct purpose: main function, example uses, sibling differentiation, and behavioral notes. No redundancy.

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?

Given the tool's simple interface (2 params, 100% schema coverage, with output schema), the description fully covers purpose, usage guidelines, behavioral traits, and parameter semantics. Annotations and output schema description fill remaining gaps.

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 meaningful context beyond the schema: notes that string inputs handle beyond JS-safe range, magnitude must be below 10^36, and non-integers/floats are rejected. This aids the agent in correct parameter usage.

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?

The description clearly states the tool's primary function: converting integers to English or Spanish words. It specifies the number scale (short/long), language options, magnitude limit, and input types. It also distinguishes itself from sibling tools like conversion_string_number and math_roman_numerals_converter.

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

Usage Guidelines5/5

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

The description explicitly guides when to use this tool (for cardinal text in cheques, legal copy, accessibility) and provides clear alternatives for related tasks (conversion_string_number for free-form numeric format conversion, math_roman_numerals_converter for Roman numerals).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server