Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

conversion_binary_decimal

Read-onlyIdempotent

Convert a single number between binary (base 2) and decimal (base 10) in either direction. Supports signed or unsigned interpretation, 8/16/32/64-bit width, and optional fractional parts.

Instructions

Binary And Decimal Number Converter. Convert a single number between binary (base 2) and decimal (base 10) in either direction, with unsigned or signed (two's-complement) interpretation across an 8/16/32/64-bit width and optional fractional (radix-point) support. Use this when you need bit-level detail for one number — a positional bit breakdown and two's-complement handling at a fixed width. Use conversion_base_converter instead to convert one integer between arbitrary radixes 2-36, conversion_number_base to map a string of byte values across ASCII/binary/hex/decimal/octal, and conversion_decimal_hex for decimal-hex conversions. Runs locally via the shared logic runner: read-only, non-destructive, offline, no auth, default rate limit. Returns the converted string plus the echoed settings and, for binary-to-decimal, a per-bit breakdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesConversion direction.
inputYesThe number to convert. For binary-to-decimal, digits 0/1 with an optional fractional part (e.g. "1010" or "101.1"). For decimal-to-binary, a decimal value with optional sign/decimal point (e.g. "-42" or "5.25"). Leading/trailing whitespace is trimmed.
numberTypeNoInterpretation of the value. 'signed' enables two's-complement at the given bitWidth; 'unsigned' treats it as non-negative.unsigned
bitWidthNoFixed width for signed (two's-complement) interpretation. Required to be one of the enum values when numberType is 'signed'; ignored for unsigned.
allowFractionalNoWhen true, permits a fractional (radix-point) part; when false, a fractional input is rejected with an error.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when conversion succeeded; false on validation error.
resultNoThe conversion result (present when success is true).
errorNoError message (present when success is false).
Behavior5/5

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

Beyond annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true), the description adds important behavior: runs locally, offline, no auth, default rate limit. Also describes return value structure.

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?

The description is well-structured and concise, front-loading purpose and usage, then behavior. Every sentence adds value without redundancy.

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?

Despite the tool's complexity (5 parameters, multiple modes, fractional support, signed/unsigned, bit width), the description covers essential usage, behavioral traits, and return value. Paired with output schema and annotations, it's complete.

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 coverage is 100% with good parameter descriptions. The description adds minimal per-parameter meaning beyond the schema, but includes global context. Baseline 3 is appropriate.

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 the tool converts a single number between binary and decimal, with specific details about direction, bit width, and fractional support. It distinguishes from siblings by naming alternative tools.

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 says when to use this tool (bit-level detail for one number) and when to use alternatives (conversion_base_converter, conversion_number_base, conversion_decimal_hex). 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