Skip to main content
Glama

number_base_convert

Read-onlyIdempotent

Convert numbers between binary, octal, decimal, hexadecimal, or any base 2–36 by setting input and output bases.

Instructions

Convert numbers between binary, octal, decimal, hex, and any base 2-36.

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": {
      "value": "<value>"
    },
    "name": "number_base_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesNumber to convert.
to_baseNoOptional custom output base (2-36).
from_baseNoInput base (2-36, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the supported base range, but does not describe output format, invalid-input behavior, or case sensitivity.

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?

A single, front-loaded sentence with no filler. It communicates the core operation and supported base range efficiently.

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, read-only conversion utility with complete parameter descriptions and rich annotations, the description is sufficient. It could mention output representation, but no output schema exists and the operation is straightforward.

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%, so value, from_base, and to_base are already documented. The description reinforces the base range but adds no syntax or formatting details beyond the schema.

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 numbers between base systems, including binary, octal, decimal, hex, and arbitrary bases 2-36. It is clear what the tool does, though it does not differentiate itself from the sibling base_convert tool.

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 description, but it gives no explicit conditions for choosing this tool over base_convert or the other conversion tools. No when-not or alternative guidance is provided.

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

Deploy Server

Other Tools