Skip to main content
Glama

Base64 Encode / Decode API - text or files

base64_encode_decode
Read-onlyIdempotent

Encode text or a file to Base64 or decode Base64 back, with URL-safe variant. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/base64-encode-decode.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "encode",
      "text": "hello"
    },
    "name": "base64_encode_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoencode or decodeencode
textNoThe text
filesNoOr several files: [{fileName, fileContent (base64)}]
urlSafeNoURL-safe alphabet (- and _)
fileNameNoFile name with extension, e.g. report.pdf
fileContentNoOr send a file as base64 (a data: URI is fine) instead of text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations only declare safety/idempotency (readOnlyHint, idempotentHint, openWorldHint). The description goes well past them by disclosing data handling ('runs on our server, files are deleted right after the call, nothing stored') and commercial constraints (25 calls/day per IP free, $0.001 per call via x402). That is exactly the kind of context an agent needs, and nothing here contradicts the annotations. It stops short of a 5 only because response shape and failure behavior are not mentioned.

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?

Two sentences, capability first, then operational terms, with no filler. The pricing/URL clause is long but operationally relevant. Slight cost: the commercial terms dominate the second half and push the file-vs-text distinction out of focus.

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 6-parameter, zero-required, annotation-light tool with no output schema, the description supplies the missing privacy, quota, and cost context an agent would otherwise lack. The notable remaining gap is that the return value must be inferred entirely from the operation, since there is no output schema and no described response format.

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 every parameter (mode, text, files, urlSafe, fileName, fileContent) is already documented in the schema, including the enum values and the data: URI allowance. The description echoes the same information at a high level ('text or a file', 'URL-safe variant') without adding format detail, syntax, or constraints beyond it. Baseline 3 is appropriate.

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 names a specific verb pair and resource: 'Encode text or a file to Base64 or decode Base64 back, with URL-safe variant.' That is a concrete transform over clear inputs. It never names a sibling tool or states how it differs from url_encode_decode, so it meets the 'clear but no sibling differentiation' bar rather than the top one.

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 operation itself (encode payloads, decode Base64 strings), but the description gives no explicit when-to-use or when-not guidance, and no prerequisites for choosing between the text path, the file path, and the URL-safe variant. The agent must infer all routing from the schema.

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.

Resources