Skip to main content
Glama
MCP Toolkit

MCP Toolkit

base64_convert

Encodes UTF-8 text to Base64 or decodes strict Base64 back to UTF-8, helping developers convert text for data transport and storage.

Instructions

Encode UTF-8 text to Base64 or decode strict Base64 into UTF-8.

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>",
      "operation": "<operation>"
    },
    "name": "base64_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two real traits: UTF-8 as the text encoding and 'strict' Base64 on decode, which signals malformed input is rejected. It does not say what happens on invalid input, whether padding or whitespace is tolerated, or how errors surface, so it is only partially transparent for a tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler; the encode direction and decode direction are both stated in the fewest words possible.

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 simple two-parameter, non-destructive conversion tool with no output schema and no annotations, the description covers purpose and both parameter meanings adequately. The only real gap is error behavior on invalid Base64, which is minor for this tool class.

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 0%, so the description must compensate, and it largely does: 'text' is identified as UTF-8 text (or Base64 when decoding) and 'operation' is mapped to the encode/decode pair. What remains implicit is that the same 'text' field holds the Base64 payload in decode mode.

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 specific verbs and resources: encoding UTF-8 text into Base64 and decoding strict Base64 back into UTF-8. That is unambiguous and clearly distinct from siblings like url_encode or sha256_hash, but it never explicitly contrasts itself with any alternative, which keeps it at 4 rather than 5.

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 when-to-use guidance and no mention of alternatives such as url_encode for URL-safe contexts. The bidirectional framing implies usage, but the agent must infer the choice entirely from the operation enum in the schema.

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