Skip to main content
Glama

base64_decode

Read-onlyIdempotent

Decode a Base64-encoded string into readable text, converting encoded data back to its original form for use in workflows or debugging.

Instructions

Decode a Base64 string to text.

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": {
      "encoded": "<encoded>"
    },
    "name": "base64_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
encodedYesBase64 string to decode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds nothing beyond that: it does not say how invalid input, missing padding, or non-UTF-8 bytes are handled, which are the actual behavioral risks for a decoder. It also does not contradict the annotations.

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?

One short sentence, front-loaded with the verb and resource, with no filler. Brevity is appropriate for a trivial utility, though it leaves room for a clause on error behavior at almost no cost.

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 one-parameter pure function with full annotation coverage, the description plus schema is nearly sufficient: the agent knows input type and that output is text. The only real gap is failure behavior on malformed input, 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.

Parameters3/5

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

There is a single parameter, and schema description coverage is 100%, so the schema already documents it. The description adds no format or encoding details (padding, URL-safe variant, whitespace tolerance) beyond what the schema states, so baseline 3 applies.

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 verb and resource ('Decode a Base64 string') with the result type ('to text'), so the operation is unambiguous. It does not explicitly contrast with the closest siblings base64_encode or jwt_decode, but the name plus description leaves no realistic ambiguity.

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?

The description is purely definitional: no when-to-use conditions, no mention of the encode counterpart for round-tripping, and no guidance on what to do when input is not valid Base64. The agent must infer all of that.

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

Deploy Server

Other Tools