Scientific Calculator

Base Converter

calculator_base_convert

Read-only

Convert integers between bases 2–36 (uppercase A–Z for digits > 9).

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>",
      "from_base": "<from_base>",
      "to_base": "<to_base>"
    },
    "name": "calculator_base_convert"
  }
}

Input Schema

Name	Required	Description
`number`	Yes	Digit string in the source base.
`to_base`	Yes	Target base (2–36).
`from_base`	Yes	Source base (2–36).

Output Schema

Name	Required	Description	Default
`result`	Yes
`decimal`	No
`to_base`	No
`from_base`	No
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare this a safe, closed-world read operation, so the safety burden is lifted. The description adds one real behavioral detail — the uppercase A–Z digit alphabet for bases above 10 — but says nothing about validation behavior for invalid digits, out-of-range bases, or sign handling, which are the plausible failure modes for this tool.

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; the base range and digit convention both earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so return values and side effects need not be explained. What is missing is routing against the conversion siblings and any note on input validation or edge cases, leaving the definition adequate but with clear gaps.

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% and all three parameters are documented with examples, so the baseline is 3. The "uppercase A–Z" note is the only addition beyond the schema, and it is largely redundant with the schema's own "FF" and "Z" examples, so it does not justify going above 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?

States a specific verb and resource ("Convert integers between bases 2–36") with the supported range, so an agent knows exactly what it does. However, it never distinguishes this from the many conversion siblings (calculator_binary, calculator_hex_convert, calculator_octal_convert, calculator_decimal_convert, calculator_convert), so the 5-tier requirement of sibling differentiation is not met.

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 sentence implies the general use case but gives no when-to-use, when-not-to-use, or alternative routing. With several near-duplicate conversion tools in the sibling list, an agent gets no help deciding between this and calculator_hex_convert or calculator_convert.

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.