Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_uuencode

Read-onlyIdempotent

Encode binary data into 7-bit ASCII uuencode format for legacy email attachments, or decode uuencoded blocks back to the original content.

Instructions

UUEncode And UUDecode Binary Data. Classic Unix uuencode/uudecode: convert arbitrary text or binary into a 7-bit ASCII envelope (begin perm name ... end) and back. Set operation=encode to wrap data, operation=decode to recover it. Use this for legacy email/Usenet attachments and Unix file transfer. Prefer encoding_decoding_xxencode for 8-bit-safe Usenet variants, encoding_decoding_binhex for Macintosh resource-fork files, or encoding_decoding_base64 for modern MIME. Pure compute: read-only, non-destructive, stateless, runs offline, no auth; default rate limit 60 requests/minute. Returns the encoded/decoded result plus file_info header metadata and size stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesData to process: plain text to encode, or a full uuencoded block (begin...end) to decode.
operationYesencode wraps text into uuencode; decode extracts the original data from a uuencoded block.
filenameNoName written into the begin header (encode only); ignored on decode.data.txt
permissionsNo3-digit octal Unix mode in the begin header (encode only); ignored on decode.644

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the operation succeeded.
inputNoEcho of the submitted text.
operationNoThe operation performed.
filenameNoFilename used (encode) or parsed from the header (decode).
permissionsNoOctal mode used (encode) or parsed from the header (decode).
resultNoUuencoded block (encode) or recovered data (decode).
file_infoNoHeader metadata parsed on decode; null on encode.
statsNoSize metrics.
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and the description adds behavioral details such as 'stateless, runs offline, no auth, default rate limit 60 requests/minute'. It also discloses the return value structure: 'Returns the encoded/decoded result plus file_info header metadata and size stats.' This goes beyond annotations and provides comprehensive transparency.

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?

The description consists of three front-loaded sentences: first states the core function, second specifies operations, third gives usage guidance and alternatives. No wasted words; 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 moderate complexity (4 parameters, 2 required, 1 enum) and the presence of an output schema (stated), the description fully covers input, operation, and return values. It mentions output includes 'file_info header metadata and size stats', which complements the output schema.

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 semantic value: it explains that 'text' can be plain text or a full uuencoded block, and that 'filename' and 'permissions' are used only for encoding. This clarifies the role of each parameter beyond the schema descriptions.

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 'UUEncode And UUDecode Binary Data' with a classic Unix format, and distinguishes operations via 'operation=encode' and 'operation=decode'. It also explicitly calls out sibling tools (xxencode, binhex, base64) with specific use cases, making the purpose unmistakable.

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 says 'Use this for legacy email/Usenet attachments and Unix file transfer' and directs agents to prefer xxencode, binhex, or base64 for specific alternatives. It also notes that the tool is 'pure compute: read-only, non-destructive, stateless, runs offline, no auth; default rate limit 60 requests/minute', guiding agents on when and how to invoke it.

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