Skip to main content
Glama

encode_base64

Paid $0.02 (x402, USDC Base): Base64 encode/decode. Args: text (string), op ('enc' default | 'dec').

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": "encode_base64"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNo
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely important behavioral trait the schema cannot: the call is paid ($0.02 via x402 in USDC on Base), which affects whether an agent should invoke it casually. It does not describe failure behavior (e.g. invalid input on 'dec'), output format, or whether encoding is UTF-8 based.

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?

A single tight sentence with no filler. The one structural weakness is that the pricing clause leads the description, putting cost ahead of what the tool actually does.

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 utility with no output schema and no nested objects, the definition covers purpose, both parameters, the default op value, and the payment requirement. Only the return shape and error semantics are absent, which is a modest gap at this complexity.

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% and neither property carries a description, so the description must compensate — and it largely does, naming both params and, critically, stating that op defaults to 'enc', which the schema does not express. It stops short of clarifying encoding charset or what happens with non-string input.

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 pair: 'Base64 encode/decode'. This is unambiguous and clearly distinct from siblings like decode_jwt, get_hash, or slugify_text, though it never names a sibling to route away from.

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 when-to-use guidance at all. An agent gets no signal about when to pick this over decode_jwt for token inspection or get_hash for hashing, and no note about when encoding is appropriate versus other transforms.

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