Skip to main content
Glama

Math.Tools MCP Server

Convert Base Tool

convert-base

Convert a number from one base to another (2-64). Common shorthands: to=2 for binary, to=8 for octal, to=16 for hex. 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": {
      "number": "<number>",
      "to": "<to>"
    },
    "name": "convert-base"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget base, 2-64.
fromNoSource base, 2-64. Defaults to 10.
numberYesThe number to convert (read in the "from" base).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses the authentication requirement ('math.tools API token (numbers:* ability)') and the supported base range, which are meaningful beyond the schema. It does not describe error behavior, output format, or whether the source number is validated against the 'from' base, leaving gaps for a tool with zero annotation coverage.

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?

Three short sentences with zero waste: the core operation and range come first, then actionable shorthand examples, then the auth prerequisite. Information is front-loaded and every sentence earns its place.

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 deterministic conversion tool with full schema coverage and no output schema, the definition is nearly complete: it states the operation, base range, useful shorthands, and the auth requirement. A minor gap is the absence of any note on output format (e.g., string vs integer) or error handling for invalid inputs, but the essential calling information is present.

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 the baseline is 3. The description still adds value by mapping common target bases to their names (binary, octal, hex), which helps an agent choose parameter values beyond the schema's 'Target base, 2-64' text. It does not elaborate on 'from' or 'number' beyond the schema, but the shorthand mapping is a genuine addition.

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 states a specific verb and resource ('Convert a number from one base to another') and bounds the domain (2-64), so an agent can immediately tell what the tool does. It does not explicitly differentiate itself from siblings such as convert-numeral, leaving that distinction 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?

Usage is implied by the conversion purpose, and the shorthands (to=2 binary, to=8 octal, to=16 hex) give practical invocation guidance. However, there is no explicit statement of when to use this tool versus alternatives, nor any exclusions or prerequisite conditions beyond the token requirement.

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