Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_base91

Read-onlyIdempotent

Encode data to compact basE91 or decode back to original. Choose input format (text, hex, binary) for encoding. Ideal when smaller output size is critical.

Instructions

Base91 Encoder and Decoder. Encode bytes to basE91 or decode basE91 back to data, the densest of the ASCII-safe binary-to-text encodings: about 23% smaller than Base64 (roughly 1.23x the input size versus Base64 1.33x). Set operation to encode or decode and choose how input bytes are read with format. Prefer encoding_decoding_base91 when output size matters most; use encoding_decoding_base64 for the ubiquitous web/MIME format, encoding_decoding_ascii85 for Adobe PostScript Base85, or encoding_decoding_basex for Base32/Base58/Base85. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, idempotent, and rate-limited (60 requests/minute for anonymous callers). Returns the converted string plus size/efficiency statistics and a per-character analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput to convert: when encoding, data interpreted per format (UTF-8 text, hex, or binary digits); when decoding, a basE91 string. Must not be blank.
operationYesDirection: encode turns input into basE91; decode turns a basE91 string back into text.
formatNoHow to read text when encoding: text (UTF-8), hex (even-length hex, whitespace allowed), or binary (0/1 digits in multiples of 8 bits). Ignored when decoding.text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
inputNoThe submitted text, echoed back.
operationNoThe operation performed (encode or decode).
formatNoThe input format used for encoding (text, hex, or binary).
resultNoThe basE91 string (encode) or decoded text (decode).
statsNoSize and efficiency metrics for the conversion.
char_analysisNoDistinct output characters (encode only; empty on decode), sorted.
Behavior5/5

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

Beyond annotations (readOnly, destructive, idempotent), description adds local execution, rate limit (60 req/min), return details (converted string plus statistics and per-character analysis), and confirms no external service contact. No contradictions.

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?

Well-structured: first sentence defines purpose, then efficiency stat, then usage guidelines, then behavioral traits. Every sentence is informative and necessary.

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?

Covers all aspects: purpose, when to use, parameter roles, behavioral traits, and output summary. With output schema present, description is complete for an encoding/decoding tool.

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 has 100% coverage but description adds value by explaining operation directions and format interpretations (text/hex/binary), plus efficiency comparison. Baseline 3, description justifies 4.

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?

Clearly states 'Base91 Encoder and Decoder' with specific verb+resource, and differentiates from siblings by recommending when to use base91 vs base64/ascii85/basex.

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 says 'Prefer encoding_decoding_base91 when output size matters most' and names alternatives for other scenarios, providing clear when-to-use and when-not-to-use guidance.

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