Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_basex

Read-onlyIdempotent

Encode UTF-8 text to Base32, Base58, or Base85, or decode those formats back to text. Supports RFC 4648, Bitcoin, and Z85 alphabets.

Instructions

Base32 / Base58 / Base85 Encoder and Decoder. Encode UTF-8 text to Base32 (RFC 4648 padded), Base58 (Bitcoin alphabet, no 0/O/I/l), or Base85 (Z85-style 85-character set), or decode any of those three back to text. Pick the format with the base parameter (32, 58, or 85). Use encoding_decoding_base64 for the ubiquitous web/MIME format, encoding_decoding_ascii85 for Adobe PostScript Base85, 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 length, ratio, and efficiency statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput to convert: UTF-8 plaintext when encoding, or an encoded string in the chosen base when decoding. Must not be blank.
operationYesDirection of conversion. "encode" turns text into the chosen base; "decode" turns an encoded string back into text.
baseYesTarget alphabet. "32" = RFC 4648 Base32 with = padding; "58" = Base58 (Bitcoin alphabet); "85" = Base85 (Z85-style set).32

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
inputNoThe submitted text, echoed back.
operationNoThe operation performed ("encode" or "decode").
baseNoThe base used ("32", "58", or "85").
resultNoThe encoded string (encode) or decoded text (decode).
analysisNoLength and efficiency metrics for the conversion.
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint), the description adds critical behavioral details: 'runs locally', 'read-only, non-destructive', 'rate-limited (60 requests/minute)', and discloses return values (converted string plus statistics). No contradictions with annotations.

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?

The description is well-structured with clear sentences, each earning its place. It is slightly verbose (e.g., 'runs locally on the text you provide') but still efficient. Minor redundancy could be trimmed.

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 (all documented in schema), full schema coverage, output schema present (though not shown, description mentions statistics), and sibling context, the description is complete. No missing aspects for an agent to use it correctly.

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%, and the description adds meaning beyond schema by providing examples for text, clarifying operation direction, and detailing base format specifics (RFC 4648 padding, Bitcoin alphabet, Z85 character set). Slightly redundant with schema but still adds value.

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 identifies the tool as a Base32/58/85 encoder/decoder, specifies exact encoding standards (RFC 4648, Bitcoin alphabet, Z85), and distinguishes it from sibling tools by naming them explicitly.

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?

The description provides explicit when-to-use and when-not-to-use guidance: 'Pick the format with the base parameter' and mentions alternative tools for Base64, Ascii85, and Base91. It also notes local execution and rate limits.

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