Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Base64 decode (free)

base64_decode
Read-only

Decode Base64 to UTF-8 text. 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": {
      "encoded": "<encoded>"
    },
    "name": "base64_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
encodedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's main added value is naming the output encoding (UTF-8 text) rather than raw bytes. It says nothing about what happens on malformed or non-UTF-8 input, which is the most likely failure mode for a decode tool.

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?

Two short sentences, front-loaded with the operation and the output type. The trailing "Free." does not advance understanding of how to call the tool, but the total length is minimal and readable.

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?

For a single-parameter, no-output-schema utility this is close to adequate, and annotations cover the safety profile. Still missing the details an agent would need to call it correctly: accepted alphabet variants, padding handling, the input length cap, and error behavior on invalid input.

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

Parameters2/5

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

With one required parameter at 0% schema description coverage, the description needed to carry the parameter semantics and does not: it never states whether standard or URL-safe alphabet is accepted, whether padding is required, or that input is length-capped at 1,400,000 characters. The word "Base64" only weakly implies the input format.

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?

"Decode Base64 to UTF-8 text" is a specific verb plus resource and makes the encode/decode split against the sibling base64_encode self-evident from the name. It stops short of naming the sibling alternative explicitly, but the operation is unambiguous.

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?

The prefix "Decode Base64 to..." implies the usage context well enough that an agent knows this converts encoded payloads to plaintext. There is no statement of when not to use it, no mention of base64_encode as the inverse, and "Free" is pricing copy rather than guidance.

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