Skip to main content
Glama

encode_base85

Encode or decode text using Base85 (Ascii85) encoding. Achieves 25% overhead versus Base64's 33% for more efficient data transfer.

Instructions

Encode or decode text using Base85 (Ascii85) encoding.

Use this for more efficient encoding than Base64 — Base85 encodes
4 bytes as 5 ASCII characters, achieving 25% overhead vs Base64's 33%.

Parameters:
    text — The string to encode or decode (required).
    mode — "encode" (text → Base85, default) or "decode" (Base85 → text).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
modeNoencode

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Explains the encoding mechanism and overhead ratio, but does not disclose error handling, invalid input behavior, or output format details (e.g., delimiters, character set). Without annotations, description carries full burden.

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?

Highly concise with a front-loaded purpose statement and clear parameter list. Every sentence adds value with no redundancy.

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?

Covers input parameters and encoding concept well. Lacks details about the output format (though output schema may exist) and error handling. Still fairly complete for a simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the schema by specifying the exact values for mode (encode/decode) and clarifying that text is the input string. Since schema has no parameter descriptions, this fully compensates and provides examples.

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?

The description clearly states the verb (encode/decode) and resource (text) using Base85 encoding. It distinguishes from siblings like encode_base64 by mentioning improved efficiency and specifying the Ascii85 variant.

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 recommends using this for efficient encoding over Base64, providing a clear use case. Lacks explicit guidance on when not to use or alternative scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scotia1973-bot/api-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server