Skip to main content
Glama

Math.Tools MCP Server

Convert Numeral Tool

convert-numeral

Convert a base-10 number to another numeral system: Roman, Chinese, Egyptian, Babylonian (sexagesimal digits), or Mayan (vigesimal, real Unicode glyphs). 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": {
      "system": "<system>",
      "number": "<number>"
    },
    "name": "convert-numeral"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesThe base-10 number to convert.
systemYesThe target numeral system.

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, the description carries the full burden, and it does add real context: the required math.tools API token with numbers:* ability, and the detail that Babylonian returns sexagesimal digits while Mayan returns actual Unicode glyphs. It omits error/range behavior (Roman cannot express 0 or values above 3999), whether results are strings, and any rate-limit or failure information — significant gaps for a keyed external API call.

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 sentences, front-loaded with the action and scope, then the auth prerequisite. Every clause — the system enumeration, the sexagesimal and Unicode notes, the token requirement — carries information an agent needs.

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 two-parameter tool with full schema coverage and no output schema, this covers the essentials: what is converted, the accepted systems, and the credential requirement. It falls short only on what the returned value looks like and how out-of-range inputs are handled.

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% and the enum already constrains the five systems, so the baseline is 3. The description adds only marginal meaning beyond the schema — the Babylonian and Mayan parentheticals hint at output shape rather than clarifying input semantics.

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?

States a specific verb and resource ('Convert a base-10 number to another numeral system') and enumerates the five accepted target systems with clarifying detail (sexagesimal digits, real Unicode glyphs). It implicitly separates itself from convert-base by framing the input as always base-10, but it never names that sibling, so the differentiation is left to inference.

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?

The list of exotic target systems (Roman, Chinese, Egyptian, Babylonian, Mayan) implies when this tool beats a plain base converter, but there is no explicit when-to-use or when-not-to-use statement and no mention of convert-base as the alternative for ordinary base conversion.

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