Skip to main content
Glama

encode

Convert and decode text between base64, hex, URL, HTML, JSON, Unicode, punycode, and rot13; decode JWTs and inspect code points, invisible characters, or binary payloads.

Instructions

Encode/decode: base64(url), hex, url, html, json string, unicode escapes, punycode, rot13, jwt_decode (unverified), inspect (code points, invisible chars). Binary decode -> hexdump or out_path.

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": {
      "op": "<op>"
    },
    "name": "encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYes
pathNoor a file
textNo
out_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.4/5.0
Behavior3/5

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

The annotations only declare destructiveHint=false; the description adds useful behavior detail by marking jwt_decode as unverified and describing inspect as code-point/invisible-character inspection. It does not explain whether encode/decode operations are pure, how out_path writes files, or whether existing files may be overwritten.

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 description is a compact, front-loaded list with no filler, and the binary-output note is placed after the operation list where it is useful. The telegraphic formatting is dense but still 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 an 18-operation tool with four parameters, sparse annotations, and no output schema, the description gives a good operation inventory and a few special-case notes. It does not fully explain input selection (text vs path), output for most operations, or file-write behavior, so it is only adequate rather than 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 coverage is only 25%, so the description must carry more weight; it clarifies several op values and explains that binary decode can produce a hexdump or write via out_path. It still leaves the text/path relationship and the general role of out_path underspecified beyond binary decode.

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/resource — encode/decode — and enumerates the supported encodings and transforms, including jwt_decode and inspect. That makes the tool's scope clear, but it does not explicitly differentiate it from siblings such as hash or json, so it falls short of the top score.

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 operation list implies the kinds of tasks this tool handles, and 'Binary decode -> hexdump or out_path' gives a concrete output choice. It does not say when to use this instead of alternatives or when not to use it, so guidance is only implied.

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