SmartTools

Number base converter

number_base

Convert an integer between bases 2–36 (binary, octal, decimal, hex and more), exact for 64-bit values via BigInt. Runs on smart-tools.xyz.

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

Input Schema

Name	Required	Description
`value`	Yes	The integer to convert (may use 0x/0b/0o prefix, spaces or _ as separators)
`locale`	No	Language for the source_url link (default en)
`to_base`	No	Base to convert to, 2–36
`from_base`	Yes	Base of the input, 2–36

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It adds value by stating 'exact for 64-bit values via BigInt' and limiting to integers. However, it does not disclose error handling, return format, or other behavioral details that might be expected from a conversion tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the core purpose. The second sentence 'Runs on smart-tools.xyz' is unnecessary filler but does not significantly detract. Overall, it is well-structured for a simple tool.

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?

The description explains inputs (integer, bases 2–36) and precision (BigInt) but does not describe the output format or return value. Since no output schema exists, this is a notable gap. It is adequate but incomplete for a converter without an output schema.

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% for all parameters, and each parameter has a clear description. The tool description adds no additional meaning beyond what the schema already provides, so 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 an integer between bases 2–36, with specific examples (binary, octal, decimal, hex). This distinguishes it from sibling converter tools like angle_converter or area_converter.

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

Usage Guidelines4/5

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

The intended use is clear: convert integers between base systems. No alternatives or exclusions are mentioned, but given the distinct purpose, context is sufficient. It does not explicitly say when not to use it, but the tool's scope is well-defined.

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

All SmartTools 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.

Resources

Need Help?