Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_ascii85

Read-onlyIdempotent

Encode text to ASCII85/Base85 or decode ASCII85 back to text, using Adobe PostScript character set with optional compression. Runs locally and returns converted string plus statistics.

Instructions

ASCII85 / Base85 Encoder and Decoder. Encode text to ASCII85 (Base85) or decode ASCII85 back to text, using the Adobe PostScript character set with optional z (4 zero bytes) and y (4 space bytes) compression. ASCII85 packs 4 bytes into 5 characters (~25% smaller than Base64's 4-into-6); use encoding_decoding_base64 for the ubiquitous web/MIME format, or encoding_decoding_base91 for the most compact ASCII-safe output. Runs locally on the text you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the converted string plus size and efficiency statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput to convert: UTF-8 plaintext when encoding, or an ASCII85 string when decoding. Must not be blank.
operationYesDirection: "encode" turns text into ASCII85; "decode" turns an ASCII85 string back into text.
optionsNoOptional encode-time settings (ignored when decoding, since delimiters and whitespace are auto-detected).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
inputNoThe submitted text, echoed back.
operationNoThe operation performed ("encode" or "decode").
optionsNoThe effective encode options after defaults were applied.
resultNoThe ASCII85 string (encode) or decoded text (decode).
statsNoSize and efficiency metrics for the conversion.
Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint; description adds that it runs locally, is non-destructive, contacts no external service, and has a rate limit of 60 requests/minute for anonymous callers, fully disclosing behavior.

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?

Description is well-structured: first sentence states purpose, then details compression, sibling differentiation, behavioral notes, and what is returned. Every sentence adds value; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 3 parameters with nested objects, an output schema, and moderate complexity, the description is thorough. It covers all aspects: direction, compression, local execution, rate limits, and return value (size and efficiency stats). Output schema handles return details.

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

Parameters4/5

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

Schema coverage is 100% with detailed descriptions for each parameter. Description adds value by explaining z and y compression and clarifying that options are only for encoding, but schema already covers individual fields well.

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?

Description clearly states it is an ASCII85/Base85 encoder and decoder, specifies the Adobe PostScript character set with optional z and y compression, and distinguishes from sibling tools (base64 and base91).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool versus alternatives (base64 for web/MIME, base91 for compact output), and notes that it runs locally with rate limits, helping the agent choose appropriately.

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/Jambozx/onlinecybertools-mcp-server'

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