Skip to main content
Glama

encode_base64

Encode text to Base64 for safe transport in JSON, URLs, or email. Decode Base64 back to original text.

Instructions

Encode or decode text using Base64.

Use this when you need to encode binary data for text-safe transport
(e.g., in JSON, URLs, or email) or decode previously encoded Base64 data.

Parameters:
    text — The string to encode or decode (required).
    mode — Operation: "encode" (text → Base64) or "decode" (Base64 → text)
           (default: "encode").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
modeNoencode

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the two modes (encode/decode) but does not mention error handling (e.g., invalid Base64 input) or output format details.

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 very concise: two short paragraphs plus a parameter list. Every sentence adds value, and the purpose is front-loaded.

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?

Given the low complexity and presence of an output schema, the description covers the essential operations. A brief note about invalid input handling would improve completeness, but it's adequate for most uses.

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

Parameters5/5

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

Schema description coverage is 0%, but the description provides clear, detailed explanations for both parameters (text and mode) including their values and defaults, fully compensating for the schema gap.

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 clearly states the tool encodes or decodes Base64 text. It provides a specific verb-resource pair but does not explicitly distinguish from sibling tools like encode_base32 or encode_base85.

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 gives explicit use cases (encode for text-safe transport, decode previously encoded data). However, it lacks guidance on when not to use it or alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scotia1973-bot/api-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server