Skip to main content
Glama

Encode, decode or hash text

encode_text
Read-onlyIdempotent

Base64, base64url and URL encoding or decoding of text, or a hash (SHA-256, SHA-512, SHA-1, MD5) in hex and base64.

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>",
      "mode": "<mode>"
    },
    "name": "encode_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesOperation.
textYesText to transform (UTF-8).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Operation"New value: +"Operation."
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "base64_encode",
      -  "base64_decode",
      -  "base64url_encode",
      -  "base64url_decode",
      -  "url_encode",
      -  "url_decode"
      -]New value: +[
      +  "base64_encode",
      +  "base64_decode",
      +  "base64url_encode",
      +  "base64url_decode",
      +  "url_encode",
      +  "url_decode",
      +  "hash_sha256",
      +  "hash_sha512",
      +  "hash_sha1",
      +  "hash_md5"
      +]
    • changedInput schema / properties / text / description
      Previous value: -"Text to encode or decode"New value: +"Text to transform (UTF-8)."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered by structured data. The description usefully adds that hashes are produced in hex and base64 and that input is treated as UTF-8 text, but it says nothing about error behavior for invalid base64 or unsupported URL sequences, which is the main runtime risk.

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 dense sentence, front-loaded with the operation family, with no filler or repetition of the title. It is efficiently sized for a two-parameter utility.

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 simple two-parameter transformation tool with full schema coverage and complete annotations, the description covers the necessary surface. The one remaining gap is the unspecified hex-versus-base64 choice for hash outputs and decode failure behavior.

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% with an enum for mode and a documented text parameter, so the baseline is 3. The description adds the algorithm and dialect vocabulary and the output format for hashes, but leaves ambiguous whether hex or base64 is selectable or how, since no separate parameter exists for it.

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 the resource (text) and the operations (encode, decode, hash) plus the concrete dialects and algorithms, so an agent knows exactly what the tool does. It does not differentiate against plausible siblings such as convert_data, inspect_json, or compare_texts, so it stops short of a 5.

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?

There is no guidance on when to choose this tool over alternatives like convert_data or parse_url, and no stated preconditions such as input size limits or that decode modes fail on malformed input. Usage is only inferable from the mode enum values, which the description does not discuss.

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.