Skip to main content
Glama
Sign In

IA-QA — 152 QA & Dev Tools for AI Agents

by io.github.JcJamet
OverviewDiscussionsAdmin

number_base_convert

Read-onlyIdempotent

Convert numbers between bases: decimal, binary, octal, hexadecimal, or any base 2–36. Auto-detects 0x, 0b, 0o prefixes.

Input Schema

NameRequiredDescriptionDefault
inputYesNumber to convert (e.g., "255", "0xFF", "0b1010", "0o77")
to_baseNoTarget base 2–36 (omit to get all common bases)
from_baseNoSource base 2–36 (auto-detects prefix if omitted)

Output Schema

NameRequiredDescriptionDefault
octalNo
binaryNo
resultNo
decimalNo
to_baseNo
from_baseNo
hexadecimalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "from_base": 16,
+    "input": "ff",
+    "to_base": 10
+  }
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / from_base / description
      Previous value: -"Source base 2–36 (auto-detects prefix if omitted)"New value: +"Source base 2–36 (auto-detects prefix if omitted)"
    • changedInput schema / properties / to_base / description
      Previous value: -"Target base 2–36 (omit to get all common bases)"New value: +"Target base 2–36 (omit to get all common bases)"
  3. Changed1 schema field changed
    • addedOutput schema / properties
      Added value: +{
+  "binary": {
+    "type": "string"
+  },
+  "decimal": {},
+  "from_base": {},
+  "hexadecimal": {
+    "type": "string"
+  },
+  "octal": {
+    "type": "string"
+  },
+  "result": {
+    "type": "string"
+  },
+  "to_base": {}
+}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds real behavior beyond that: prefix auto-detection for 0x/0b/0o and the implicit default of returning all common bases when to_base is omitted.

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?

Two short sentences, zero filler, with the supported-scope clause front-loaded ahead of the auto-detect detail.

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?

An output schema exists, so return values need no explanation, and the base-range plus prefix behavior round out the core contract. The remaining gap is the unprefixed-input assumption and out-of-range/invalid-input behavior, which an agent would need to guess.

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% and both to_base/from_base descriptions already state the 2–36 range and prefix auto-detection, so the description largely restates the schema. It adds no clarification for the ambiguous unprefixed case (e.g. whether '11' is decimal or binary).

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?

States a specific verb ('Convert') plus resource ('numbers between bases') and enumerates the supported base families and the 2–36 range. An agent can distinguish this from siblings like base64_encode or color_convert purely from the text.

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

Usage Guidelines3/5

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

Usage is implied by the narrow domain, but there is no explicit when-to-use or when-not framing. Notably, it does not rule out the most plausible sibling confusion — base64_encode/base64_decode, which also 'convert' representations of data — so the agent must infer the boundary itself.

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

All IA-QA — 152 QA & Dev Tools for AI Agents toolsInspect
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