Skip to main content
Glama

dev_tools_base64

[$x402 pago por llamada] Codifica o decodifica texto en Base64 estándar.

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": {
      "input": "<input>"
    },
    "name": "dev_tools_base64"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo`encode` o `decode`. Por defecto `encode`.
inputYesTexto de entrada.
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

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?

No annotations are provided, so the description carries the full burden, and it does disclose one important trait: the call is x402-paid, implying a 402 response without a payment header. Beyond that it says nothing about padding/variant behavior, error handling, or the shape of the result, so the disclosure is partial rather than thorough.

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 tightly written sentence with no filler; the bracketed payment tag leads, and the core action follows immediately. Slight oddity is that a billing marker precedes the tool's actual purpose.

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 simple 3-parameter transform with no output schema and no annotations, the essentials are covered by the schema, but the description omits what comes back (a string in the selected mode) and any failure modes outside the 402 path. Adequate, not complete.

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 description coverage is 100%, so mode, input, and x_payment are already fully documented. The phrase 'Base64 estándar' adds a small hint that no URL-safe or padding variant applies, but the description otherwise adds nothing beyond the schema's own text.

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: encode or decode text as standard Base64. The operation is unambiguous, though it offers no differentiation from a closely related sibling such as dev_tools_hex, which handles an analogous transform.

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 never says when to use this tool versus the hex encoder or other text transforms, and gives no conditions or exclusions. Only the payment note hints at invocation context, not tool selection.

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