Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_base64

Read-onlyIdempotent

Encode UTF-8 text to standard Base64 (RFC 4648) with padding, or decode Base64 back to UTF-8. Ignores whitespace in decode input and validates payload.

Instructions

Base64 Encoder and Decoder. Convert UTF-8 text to standard Base64 (RFC 4648, +/ alphabet, = padding) or decode Base64 back to text. Whitespace in decode input is ignored and the payload is validated before decoding. This handles text only — to Base64-encode an uploaded file or a data URI use file_base64_file_encoder, for images use webdev_base64_image_encoder, and for Base32/Base58/Base85 use encoding_basex or encoding_ascii85. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/min, 500/hour, 2000/day for anonymous callers). Returns the transformed string alongside the echoed input and operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe payload to process. For encode, the plain UTF-8 text to convert to Base64; for decode, the Base64 string to convert back to text (surrounding whitespace and newlines are stripped). Must not be blank.
operationYesDirection of conversion: 'encode' turns text into Base64; 'decode' turns valid Base64 back into text. Invalid Base64 on decode returns an error.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the conversion succeeded.
inputNoThe original text submitted, echoed back.
operationNoThe direction requested; either encode or decode.
resultNoThe converted output — Base64 for encode, decoded UTF-8 text for decode.
Behavior5/5

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

Adds details beyond annotations: ignores whitespace on decode, validates payload, runs locally, is read-only, rate-limited, and describes return format.

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?

Every sentence is informative, front-loaded with purpose, no redundancy, well-structured.

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 input, output, behavior, alternatives, constraints; output schema present; no gaps for a text encoding tool.

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

Parameters3/5

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

With 100% schema coverage, the description mostly repeats schema info; adds no significant new meaning beyond what is already in the schema.

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 it is a Base64 encoder/decoder for UTF-8 text, and distinguishes from sibling tools for files, images, and other bases.

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 states when to use (text only) and when to use alternatives (file, image, other bases), providing clear 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