Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

conversion_morse

Read-onlyIdempotent

Encode plain text to International Morse Code or decode Morse back to text. Maps A-Z, 0-9, and punctuation to dot/dash patterns.

Instructions

Morse Code Encoder And Decoder. Encode plain text to International Morse Code or decode Morse back to text. Encoding upper-cases input and maps A-Z, 0-9 and common punctuation to dot/dash patterns, joining letters with a single space and words with a slash; unsupported characters become the Morse for a question mark. Decoding splits on the slash for words and spaces for letters and emits a question mark for any unrecognised symbol. Use this for dot-dash signalling; use conversion_braille for tactile braille cells and encoding_decoding_baconian for the A/B Baconian cipher. Runs locally on the supplied text: read-only, non-destructive, offline, no auth, default rate limit. Returns the converted string plus an analysis block (symbol/character counts, ratios) and reference morse_info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput to convert: plain text when operation is encode, or a Morse string (dots, dashes, spaces between letters, a slash between words) when operation is decode. Trimmed; must be non-empty. Unsupported text characters encode to the Morse for a question mark; unrecognised Morse tokens decode to a question mark.
operationYesencode converts text to Morse code; decode converts Morse code to text. Required; any other value returns a 400 error.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
resultNoThe converted output: Morse code for encode, Latin text for decode.
analysisNoPer-conversion stats (operation, input_length, output_length, compression_ratio, character_stats, morse_stats: dots, dashes, total_symbols, word_separators, char_separators, dot_dash_ratio); null on error.
morse_infoNoReference facts (name, description, dot_duration, dash_duration, char_separator, word_separator, supported_chars, inventor, standard, common_uses).
errorNoError message, present only when success is false.
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint), the description adds detailed behavioral traits: encoding upper-cases input, mapping to dot/dash patterns, joining with spaces and slashes, handling unsupported characters, decoding splits on slashes and spaces, and emitting question marks for unrecognized symbols. No contradiction 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.

Conciseness5/5

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

The description is well-structured, front-loading the purpose, then behavioral details, usage guidance, safety notes, and return value format. Every sentence adds value without redundancy.

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 presence of an output schema, the description still explains the return format ('converted string plus an analysis block and reference morse_info'). Covers encoding and decoding behaviors, constraints, and alternatives comprehensively.

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%, so baseline is 3. The description adds value by specifying that text must be non-empty and trimmed, and explains behavior for unsupported characters during encoding and decoding, which is not fully covered in 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 it is a Morse Code Encoder and Decoder, with specific verb+resource. It distinguishes itself from sibling tools like conversion_braille and encoding_decoding_baconian by mentioning 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?

Explicit guidance is given: 'Use this for dot-dash signalling; use conversion_braille for tactile braille cells and encoding_decoding_baconian for the A/B Baconian cipher.' It also states that it runs locally and is non-destructive.

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