Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_caesar

Read-onlyIdempotent

Encode or decode text using the classical Caesar shift cipher, rotating each letter by a fixed number of positions (1-25) through the alphabet.

Instructions

Caesar Cipher (Encode / Decode). Encode or decode text with the classical Caesar shift cipher: each A-Z letter is rotated a fixed number of positions (1-25) through the alphabet, decode applying the inverse rotation. This is a monoalphabetic substitution cipher with no real cryptographic strength — identical letters always map identically and frequency patterns survive, so use it for puzzles, CTFs, and learning, not to protect secrets. Use encoding_decoding_rot13 for the fixed ROT13/ROT47 variant (shift 13), or encoding_decoding_vigenere when you need a keyword-driven polyalphabetic shift instead of one fixed value. Out-of-range or non-integer shifts are rejected; preserve_case and preserve_non_alpha control whether original casing and non-letter characters are kept. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited. Returns the transformed text, a human-readable info string, and a letter-frequency analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to transform. Only A-Z/a-z letters are shifted; other characters are passed through or dropped per preserve_non_alpha.
operationYesWhether to encode (shift forward) or decode (shift backward by the same amount).
shiftYesNumber of alphabet positions to rotate each letter. Must be an integer 1-25; shift 13 equals ROT13 (encode and decode are identical).
preserve_caseNoKeep each letter's original upper/lower case. When false, encoded output is upper-cased and decoded output lower-cased.
preserve_non_alphaNoKeep numbers, spaces, and punctuation in the output. When false, all non-letter characters are removed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the transform succeeded.
inputNoThe input text, echoed back.
operationNoThe operation performed (encode or decode).
shiftNoThe shift value applied (1-25).
preserve_caseNoWhether original letter case was preserved.
preserve_non_alphaNoWhether non-letter characters were preserved.
resultNoThe transformed (encoded or decoded) text.
infoNoHuman-readable summary of the shift, e.g. noting when shift 13 equals ROT13.
analysisNoLetter-frequency analysis of the input text.
Behavior5/5

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

The description goes beyond the annotations to explain that the tool runs locally, is read-only, non-destructive, contacts no external service, and is rate-limited. It also details behavior for out-of-range shifts (rejected) and how preserve_case and preserve_non_alpha affect output. This fully discloses operational characteristics and is consistent with the annotations (readOnlyHint, destructiveHint, idempotentHint).

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 informative and well-structured, with each sentence serving a purpose (purpose, alternatives, behavior details, return info). It is slightly lengthy but not verbose; a minor trim could improve conciseness without losing content.

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?

The description covers all relevant aspects: tool purpose, usage scenarios, behavioral traits, parameter effects, error handling, output structure (transformed text, info string, frequency analysis), and alternative tools. It is fully complete for an AI agent to select and use the tool correctly, especially with an output schema present.

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

Parameters5/5

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

Although the input schema has 100% coverage, the description adds meaningful context: it explains that shifts 1-25 are valid and shift 13 equals ROT13, that non-integer shifts are rejected, and how the boolean parameters control case and non-alphabetic character handling. This clarifies parameter behavior beyond schema constraints and helps the agent set correct values.

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 or decodes text using the Caesar shift cipher, specifying it works on A-Z letters with shifts 1-25. It distinguishes itself from sibling tools like rot13 and vigenere by naming them and describing their different use cases, making the purpose unambiguous.

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 provides usage context: suitable for puzzles, CTFs, and learning, but not for protecting secrets. It also names alternatives (encoding_decoding_rot13 for fixed ROT13, encoding_decoding_vigenere for keyword-driven shifts) and explains when each is appropriate, giving clear guidance on when to use this tool versus others.

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