Skip to main content
Glama

base64_encode

Convert text to Base64 encoding for secure data representation or transmission.

Instructions

encode text to base64

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYestext to encode

Implementation Reference

  • The handler function for the 'base64_encode' MCP tool, registered via server.tool(). Takes a 'content' string parameter, calls Base64Util.encode() to convert it to base64, and returns the result as text content.
    server.tool(
        "base64_encode",
        "encode text to base64",
        {
            content: z.string().describe("text to encode"),
        },
        async ({ content }) => {
            const result = Base64Util.encode(content);
            return {
                content: [
                    {
                        type: "text",
                        text: result,
                    },
                ],
            };
        }
    );
  • The Base64Util.encode() helper method that performs the actual base64 encoding using Buffer.from(input).toString('base64').
    static encode(input: string): string {
        return Buffer.from(input).toString('base64');
    }
  • The input schema for the base64_encode tool, defining a single required 'content' parameter of type string (using Zod) described as 'text to encode'.
    {
        content: z.string().describe("text to encode"),
    },
  • The registerBase64Tool() function that registers both 'base64_encode' and 'base64_decode' tools on the McpServer instance.
    export function registerBase64Tool(server: McpServer) {
        // Base64 Encode
        server.tool(
            "base64_encode",
            "encode text to base64",
            {
                content: z.string().describe("text to encode"),
            },
            async ({ content }) => {
                const result = Base64Util.encode(content);
                return {
                    content: [
                        {
                            type: "text",
                            text: result,
                        },
                    ],
                };
            }
        );
    
        // Base64 Decode
        server.tool(
            "base64_decode",
            "decode base64 to text",
            {
                content: z.string().describe("base64 text to decode"),
            },
            async ({ content }) => {
                const result = Base64Util.decode(content);
                return {
                    content: [
                        {
                            type: "text",
                            text: result,
                        },
                    ],
                };
            }
        );
    }
  • src/index.ts:6-6 (registration)
    Import statement for registerBase64Tool from the base64 service module.
    import { registerBase64Tool } from "./service/base64.js";
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure, but it only states the basic operation. It does not address edge cases like empty strings or performance considerations.

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?

The description is a single, efficient sentence. It is appropriately sized for a simple tool, though slightly minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (1 param, no output schema, no annotations), the description is adequate but could mention the return format. It does not add enough context for an unfamiliar agent.

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 the baseline is 3. The description adds no additional meaning beyond the schema's parameter description.

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?

The description clearly states the tool's function: encoding text to base64. It uses a specific verb and resource, distinguishing it from sibling tools like base64_decode.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., hex_encode). The description offers no context for selection.

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/1595901624/crypto-mcp'

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