Skip to main content
Glama

Math.Tools MCP Server

Spell Number Tool

spell-number

Spell a number out in words: cardinal (e.g. "seven"), ordinal (e.g. "7th"), or currency (e.g. "seven dollars"). Requires a math.tools API token (numbers:* ability).

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": {
      "action": "<action>",
      "number": "<number>"
    },
    "name": "spell-number"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLocale for cardinal/currency, e.g. 'en_US', 'fr_FR'. Not used for ordinal (English only). Defaults to the site default.
actionYesWhich spelling to produce.
numberYesThe number to spell out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description does carry real burden, and it usefully discloses the auth prerequisite ('math.tools API token (numbers:* ability)'). However, it says nothing about rate limits, error behavior for out-of-range numbers, or whether the result is a plain string, leaving notable behavioral gaps.

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?

Two tight sentences: the capability and its three modes are front-loaded, then the auth requirement. Every clause carries information and there is no filler.

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?

For a simple three-parameter read-only formatter with full schema coverage, the definition covers purpose, modes, locale caveat, and auth. The only omission is what the return looks like, which is minor given how predictable the output is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the note that lang is unused for ordinal, so the schema already does the heavy lifting. The description's mode examples add only marginal meaning beyond the enum values and the schema's own lang caveat.

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

Purpose4/5

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

The description gives a specific verb and resource ('spell a number out in words') and enumerates three output modes with concrete examples ('seven', '7th', 'seven dollars'). It is clearly distinct from siblings like number-facts or convert-base, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied: the caller picks this when they need a number rendered as words rather than as digits or facts. There is no explicit when-not guidance and no named alternative such as convert-numeral, so the agent must infer the boundary itself.

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