Scientific Calculator

Binary ↔ Decimal Converter

calculator_binary_decimal

Read-only

Convert binary to decimal or decimal to binary.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculator_binary_decimal"
  }
}

Input Schema

Name	Required	Description	Default
`binary`	No	Binary string for binary→decimal.
`decimal`	No	Decimal integer for decimal→binary.
`direction`	No	auto\|binary_to_decimal\|decimal_to_binary	auto

Output Schema

Name	Required	Description	Default
`binary`	No
`decimal`	No
`direction`	No
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description does not contradict them, but it adds little beyond the basic conversion behavior and does not clarify auto-direction behavior or validation.

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?

It is a single sentence with zero waste and is front-loaded with the core operation. For a simple converter, this is appropriately sized.

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?

The tool is simple, the schema is fully documented, annotations cover safety, and an output schema exists. The description is complete enough to call the tool, though it lacks sibling routing context in a crowded calculator namespace.

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 the binary, decimal, and direction parameters are already documented in the schema. The description adds no semantics beyond the schema baseline.

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 between binary and decimal. It is clear what the tool does, but it does not distinguish this tool from overlapping siblings such as calculator_binary, calculator_decimal_convert, calculator_base_convert, or calculator_convert.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description identifies the two conversion directions but gives no guidance on when to use this tool instead of related converters, nor does it explain how to choose direction or handle the auto case. Usage is only implied by the tool name and purpose.

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

All Scientific Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.