Skip to main content
Glama
The-40-Thieves

codecalc

by The-40-Thieves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Radix Convert

radix_convert
Read-onlyIdempotent

Convert digits between bases 2-36, handling fractions and flagging non-terminating results in the target base.

Instructions

Convert a value between ANY bases 2..36, fractions included; bases that cannot represent the fraction (e.g. 0.1 in base 2) are flagged non-terminating. radix_convert('zz', 36, 7) is one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesDigit string to convert (fractions with '.' accepted), in `from_base`
to_baseNoBase to convert `value` into; valid range 2..36, default 10
from_baseNoBase `value` is written in; valid range 2..36, default 10

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.0
    • addedInput schema / properties / from_base / description
      Added value: +"Base `value` is written in; valid range 2..36, default 10"
    • addedInput schema / properties / to_base / description
      Added value: +"Base to convert `value` into; valid range 2..36, default 10"
    • addedInput schema / properties / value / description
      Added value: +"Digit string to convert (fractions with '.' accepted), in `from_base`"
  2. Changed1 schema field changedv0.11.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "radix_convertDictOutput",
+  "type": "object"
+}
  3. Changed6 schema fields changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / from_base / title
      Added value: +"From Base"
    • addedInput schema / properties / to_base / title
      Added value: +"To Base"
    • addedInput schema / properties / value / title
      Added value: +"Value"
    • addedInput schema / title
      Added value: +"radix_convertArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  4. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds genuinely useful behavior: fractions are accepted and non-terminating results are flagged, with an example showing the call shape. It does not contradict any annotation.

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 two tight sentences that immediately state scope and a key edge-case behavior, then give a compact example. Every clause earns its place with no fluff or repetition of schema details.

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 description covers the base range, fraction handling, non-terminating behavior, and an example, which is sufficient for a moderate-complexity read-only tool. An output schema exists, so the absence of return-format details is acceptable. It is complete enough for an agent to select and invoke the tool correctly.

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 baseline is 3, and the schema already explains each parameter and ranges. The description adds an example call, but the positional order in `radix_convert('zz', 36, 7)` is ambiguous against the schema's property order (value, to_base, from_base), which may confuse an agent. Thus it adds some value but also introduces uncertainty.

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 states a specific verb ('Convert'), a precise resource ('a value between ANY bases 2..36'), and a distinctive scope ('fractions included'). This clearly differentiates it from sibling tools like convert_units or float_repr, and the example reinforces the purpose.

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 description conveys clear usage context: any base between 2 and 36, with fraction support and non-terminating detection. It does not explicitly name alternatives or exclusions, but for a general-purpose conversion tool the domain is unambiguous. The sibling list contains no close competitor that would require an explicit 'use X instead' note.

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

Deploy Server

Other Tools