Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_binhex

Read-onlyIdempotent

Encode text to BinHex 4.0 (HQX) format or decode a BinHex stream back to text, preserving Finder metadata like filename, type, and creator codes.

Instructions

BinHex Encoder and Decoder. Encode text to BinHex 4.0 (HQX) or decode a BinHex stream back to text. BinHex is the classic Macintosh binary-to-ASCII format that wraps a file's data fork plus Finder metadata (filename, 4-char type and creator codes) and CRC checksums into a 7-bit ":...:" envelope for email and cross-platform transfer. Use encoding_decoding_uuencode or encoding_decoding_xxencode for Unix/Usenet files, encoding_decoding_base64 for the ubiquitous web/MIME format, or encoding_decoding_ascii85 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; decoding also returns the recovered filename, type, creator, and byte size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput to convert: UTF-8 plaintext when encoding, or a BinHex 4.0 stream (the ":...:" block) when decoding. Must not be blank.
operationYesDirection: encode wraps text into a BinHex 4.0 envelope; decode recovers the original text and Finder metadata from a BinHex stream.
filenameNoEncode-only: filename stored in the BinHex header (truncated to 63 bytes). Ignored when decoding (filename is read from the stream).data.bin
typeNoEncode-only: 4-character Macintosh Finder file type code (padded/truncated to 4 chars). Ignored when decoding.TEXT
creatorNoEncode-only: 4-character Macintosh Finder creator code (padded/truncated to 4 chars). Ignored when decoding.UNIX

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
inputNoThe submitted text, echoed back.
operationNoThe operation performed (encode or decode).
filenameNoEncode: the filename you supplied. Decode: filename recovered from the BinHex header.
typeNoEncode: the type code you supplied. Decode: type code recovered from the header.
creatorNoEncode: the creator code you supplied. Decode: creator code recovered from the header.
sizeNoDecode only: byte length of the recovered data fork.
resultNoEncode: the BinHex 4.0 envelope string. Decode: the recovered file contents as text.
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds valuable context: runs locally on provided text, contacts no external service, rate-limited (60 requests/minute), and returns converted string plus metadata on decode. 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.

Conciseness4/5

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

The description is a single paragraph but efficiently packs all key info without redundancy. It could be slightly more structured (e.g., bullet points for alternatives), but every sentence earns its place.

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's complexity (5 parameters, 2 required, output metadata), the description covers purpose, usage, behavior, parameters, and returns comprehensively. It also references output schema implicitly (decoding returns filename, type, creator, size). Well-contextualized among many siblings.

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 descriptions for all 5 parameters. The description adds extra meaning: explains default values, truncation rules for filename/type/creator, and that some parameters are ignored on decode. This goes beyond schema documentation.

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 tool encodes text to BinHex 4.0 or decodes BinHex to text, with specific verb+resource+format. It distinguishes from siblings by listing alternative encodings (uuencode, xxencode, base64, ascii85) and their use cases.

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 explicitly states when to use BinHex (classic Macintosh binary-to-ASCII) and when not to (for Unix/Usenet use uuencode/xxencode, for web/MIME use base64, etc.). It also notes the tool is read-only and non-destructive, providing clear context.

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