Skip to main content
Glama

Translate Morse code

translate_morse
Read-onlyIdempotent

Translates text to Morse code or Morse code to text. Returns the result, a letter-by-letter breakdown with the dot and dash patterns, the signal timing at the chosen speed and a link to the SandiMorse translator with the same input. The widget plays the sound and blinks a lamp.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "translate_morse"
  }
}

Input Schema

NameRequiredDescriptionDefault
wpmNoSending speed in words per minute for the timing. Default 15.
textYesThe text to translate, or Morse code written with dots and dashes (letters separated by spaces, words by /).
languageNoLanguage of the answer and of the page the link opens: id for Indonesian or en for English. Default id.
directionNotext_to_morse (default) or morse_to_text.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the shape of the output (letter-by-letter breakdown, timing at the chosen speed, shareable link) and the widget side effects of playing sound and blinking a lamp — useful for an agent deciding whether this tool has observable effects.

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?

Two sentences, front-loaded with the core action and then the return contents. Every clause carries information; the widget sentence is slightly tangential but still conveys observable behavior, so nothing is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't enumerate return fields, and it still gives a useful summary of them. It also covers side effects and the link behavior. Only gaps are error conditions and input constraints, which the schema already enforces (maxLength 300, wpm 5–30).

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?

Schema description coverage is 100%, so direction, wpm, language and text are all documented in the schema. The description only indirectly references parameters ('at the chosen speed', 'same input'), adding little beyond what the schema already provides, so the baseline of 3 applies.

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?

Names a specific verb and resource ('Translates text to Morse code or Morse code to text') and states the bidirectional scope explicitly. This clearly separates it from siblings like morse_chart or morse_practice, which do not perform translation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the bidirectional phrasing, but the description gives no explicit when-to-use guidance or conditions that would route an agent here versus encode_scout_code, decode_scout_code, or morse_chart. No exclusions or prerequisites are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.