Skip to main content
Glama

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

Encoding toolbox: Base64, hex, URL, HTML and Unicode

pack_encoding_toolbox
Read-only

Every common encoding of one text in a single call: Base64 and Base64url, hex, URL component and full-URL encoding, HTML-escaped, ROT13, Unicode code points, UTF-8 byte count and Punycode for international domain names, plus automatic decoding when the input already looks like Base64, hex, URL or HTML encoding. Use to prepare data for headers, URLs and markup, or to work out what an encoded string says. Example: text=Café & . 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": "pack_encoding_toolbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text (up to 20,000 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, non-idempotent and closed-world. The description adds genuine context beyond them: per-call charging via x402/credits, that repeats are not free, that failed calls are free, the first 25 free, and that decoding is automatic when input looks encoded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded list of encodings, then the use case, then an example, then pricing and safety notes. It is dense but nearly every clause carries information an agent needs to decide and call correctly.

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?

With no output schema, the description partially carries the burden of explaining results by enumerating what is computed, plus noting failed calls are free. It stops short of describing the response shape for a multi-encoding result.

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?

Only one parameter, and the schema already documents it fully at 100% coverage including the 20,000-character limit. The description adds an illustrative example value and the auto-decode behavior, but no input format rules beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb-and-resource: enumerates Base64/Base64url, hex, URL, HTML, ROT13, Unicode code points, UTF-8 byte count and Punycode, plus automatic decoding. It distinguishes itself from siblings such as base64_encode or url_encode by covering every common encoding in one call.

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?

Explicitly says when to use it: to prepare data for headers, URLs and markup, or to work out what an encoded string says. It implies the single-encoding siblings as alternatives but never names them or states explicit 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.