Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Base64 decode: decode base64 or URL-safe base64 back to text

base64_decode
Read-only

Decode standard or URL-safe base64 to UTF-8 text. Missing padding is tolerated. Use to read encoded headers, tokens and data URLs. Example: text=aGVsbG8gd29ybGQ=. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "base64_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe base64 text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description corroborates with "reads or computes only and changes nothing." It usefully explains the non-obvious idempotentHint=false (each call is billed, failed calls free) and discloses padding tolerance, but says nothing about how invalid input is reported, which matters for a decoder.

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?

Front-loaded with the operation and the padding rule, then usage, then billing; nothing is buried. The pricing/credits sentence is long but carries decision-relevant cost information, so it earns its place, though it could be tightened.

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 one-parameter, annotation-covered, no-output-schema tool this covers operation, input tolerance, use cases, and cost. The only meaningful gap is error behavior on malformed base64.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is documented, so the baseline is 3; the description earns an extra point by specifying that both standard and URL-safe alphabets and unpadded input are accepted, plus a worked example (text=aGVsbG8gd29ybGQ=) that the schema does not provide.

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?

"Decode standard or URL-safe base64 to UTF-8 text" states a specific verb, resource, and both input alphabets, which is enough to separate it from base64_encode and url_decode without opening a schema.

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?

"Use to read encoded headers, tokens and data URLs" gives concrete usage contexts, but it never excludes the adjacent siblings (jwt_decode for tokens, url_decode for percent-encoding), leaving the agent to infer that boundary. Clear context without exclusions fits a 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.