Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Base64 encode: encode text as base64 and URL-safe base64

base64_encode
Read-only

Encode UTF-8 text as standard base64, and also return the URL-safe variant. Use for data URLs, headers and basic auth strings. Example: text=hello world. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not 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": "base64_encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to encode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnlyHint=true and destructiveHint=false, and the description adds genuinely new behavioral facts: per-call pricing (USDC via x402 or card key), the first 25 free, failed calls free, and that repeats are charged. That last point meaningfully explains the idempotentHint=false annotation, which would otherwise look odd for a pure computation. It could still say more about output shape, but for an annotated tool this is solid added context.

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?

The core capability is front-loaded in the first sentence, followed by usage, an example, and pricing. The pricing sentence is dense but carries information an agent needs before invoking a paid tool, so it earns its place.

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 no output schema, the description does state that both standard and URL-safe encodings are returned and covers cost behavior. The remaining gap is minor: no explicit statement of the response structure (field names) despite there being no output schema to fall back on.

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% for the single 'text' parameter, so the schema already documents it fully. The description adds only that the input is UTF-8 and gives a bare example ('text=hello world'), which is marginal value over the schema. Baseline 3 applies when the schema does the heavy lifting.

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 a specific verb and resource ('Encode UTF-8 text as standard base64') and adds that the URL-safe variant is also returned, which is enough for an agent to distinguish it from base64_decode or url_encode. It stops short of explicitly contrasting with those siblings by name, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use for data URLs, headers and basic auth strings' gives concrete selection context for the tool. It does not state when to choose url_encode or base64_decode instead, so it provides context without exclusions.

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.