Skip to main content
Glama

Base64 encode/decode

bursia_base64
Read-onlyIdempotent

Encode text to base64, or decode base64/base64url back to UTF-8 text. Returns the converted text. Pure computation, 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": "bursia_base64"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoencode (default) or decode.
textYesText to encode, or base64/base64url to decode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / mode / description
      Added value: +"encode (default) or decode."
    • addedInput schema / properties / mode / enum
      Added value: +[
      +  "encode",
      +  "decode"
      +]
    • addedInput schema / properties / text / description
      Added value: +"Text to encode, or base64/base64url to decode."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds value by noting it is pure computation (no network or side effects) and free, and by stating the return value is the converted text. It doesn't mention behavior on invalid base64 input, which is the main remaining gap.

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?

Two short sentences, front-loaded with the operation and followed by the return value and cost profile. No filler, nothing that could be cut.

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 two-parameter, non-destructive conversion utility with full schema coverage and annotations, the description covers purpose, return value, and cost. Only decode-failure behavior is unaddressed, a minor omission for a tool this simple.

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% and both parameters carry descriptions, so the baseline is 3. The description reinforces that decode accepts base64 or base64url variants and that output is UTF-8 text, but adds little beyond the schema's own wording.

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?

States a specific pair of verbs (encode/decode) on a specific resource (base64/base64url to UTF-8 text), which is enough to tell it apart from neighbors like bursia_url_encode or bursia_hash. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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?

"Pure computation, free" implies the safe/cheap-utility use case, and the encode-or-decode framing tells the agent both directions exist. However, there is no explicit when-to-use vs. alternatives guidance (e.g., use bursia_url_encode for percent-encoding, bursia_hash for digests) and no statement about misuse or error conditions.

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