Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

conversion_base_converter

Read-onlyIdempotent

Convert numbers between any bases from 2 to 36, including binary, octal, decimal, and hexadecimal. Shows step-by-step conversion with decimal value and per-digit steps.

Instructions

Numeric Base / Radix Converter (Base 2-36). Convert a number from one positional numeral base to another between base 2 and base 36 (binary, octal, decimal, hexadecimal, or any arbitrary radix), with full step-by-step working. This does NUMERIC base/radix math on a single number token; for converting character-string encodings (ASCII text to/from binary, hex, decimal, or octal) use conversion_number_base instead. Input digits 0-9 and A-Z are case-insensitive and must be valid for from_base (for example base 2 allows only 0-1). Runs locally on the value you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the converted output, the decimal value, per-digit conversion steps, base metadata, and common-base representations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe number to convert, expressed in from_base. Uses digits 0-9 then A-Z (case-insensitive), must be non-blank, and every character must be valid for from_base.
from_baseNoRadix the input is written in (2-36). Defaults to 10 (decimal).
to_baseNoRadix to convert the value into (2-36). Defaults to 10 (decimal).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded; false carries an error field instead of result.
errorNoFailure message when success is false (blank input, base out of the 2-36 range, or invalid digit for from_base).
resultNoConversion payload (present when success is true).
Behavior5/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds concrete behavioral details: runs locally, no external service, rate-limited (60 req/min for anonymous). 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?

Four sentences packed with essential information, no fluff. Front-loaded with core functionality, then usage distinction, then constraints and return details.

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 output schema exists, the description summarizes return values appropriately (converted output, decimal, steps, metadata, common bases). Covers all necessary aspects for a 3-param tool.

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% with good parameter descriptions. Description adds extra context about case-insensitivity and digit validity (e.g., base 2 allows only 0-1), surpassing the schema's baseline.

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 it converts numbers between bases 2-36 with step-by-step working, and explicitly distinguishes itself from the sibling tool conversion_number_base for character-string encodings.

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?

Explicitly tells when to use this tool vs conversion_number_base: for numeric base math on a single number token, not for character-string encoding conversions. Provides clear context.

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