Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

base32

Encode text to RFC 4648 Base32 or decode it back to plaintext. Pure CPU, instant.

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": {
      "text": "<text>"
    },
    "name": "base32"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText or Base32 to process
decodeNoDecode instead of encode

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed3 schema fields changed
    • addedInput schema / properties / decode
      Added value: +{
+  "description": "Decode instead of encode",
+  "type": "boolean"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Text or Base32 to process",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "text"
+]
  4. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; 'Pure CPU, instant' does usefully disclose that this is an offline, no-network, no-side-effect transformation. It says nothing about output casing/padding conventions, case-insensitive decoding, or what happens with invalid Base32 input, which are the failure modes an agent would actually need to know.

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 clauses, operation and scope front-loaded, with no redundant restatement of the tool name. Every sentence contributes either capability or a behavioral fact.

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?

For a two-parameter stateless transform with a fully described schema and no output schema, the definition is nearly sufficient. The remaining gap is output shape (uppercase alphabet, padding presence) and error behavior on malformed Base32, both of which matter for a decode path.

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%, so both parameters are already documented in structured form. The description adds one genuinely useful piece of meaning by naming RFC 4648, which implies padding and alphabet conventions, but adds nothing about the 'decode' semantics beyond the schema's own text.

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 ('Encode text to RFC 4648 Base32 or decode it back to plaintext') and names the standard, so the operation is unambiguous. It does not explicitly distinguish itself from the many adjacent siblings (base64, base85, encode_base64), though the tool name plus the 'Base32' label makes the distinction inferable.

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?

There is no guidance on when to choose Base32 over base64/base85 or the other encoding siblings, and no prerequisites or exclusions are stated. The only usage signal is the flag documented in the schema, which the description does not reinforce or contextualize.

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

All GadgetHumans API Hub 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