Skip to main content
Glama

Morse code audio

morse_audio
Read-onlyIdempotent

Translates text into International Morse code and returns the sound as a WAV audio file (8 kHz mono), with the code as text and a link to the translator on morsecodetranslator.com. Choose the speed in words per minute (5-40, default 20) and the tone in hertz (300-1000, default 600). The sound can be at most 60 seconds long: use a higher speed or a shorter text for more.

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": "morse_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
wpmNoThe speed in words per minute, 5 to 40. Default: 20.
textYesThe text to play as Morse code, at most 200 characters.
frequencyNoThe tone in hertz, 300 to 1000. Default: 600.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's added value is the output contract: WAV, 8 kHz, mono, plus the returned code text and a link. The 60-second hard cap is a genuine behavioral constraint disclosed beyond the schema, though nothing is said about error behavior when the cap is exceeded.

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?

Front-loaded with purpose, then parameters, then the duration constraint — a logical order with no filler sentences. Some redundancy with the schema's ranges and defaults costs it a point.

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?

With no output schema, the description carries the full burden of describing return values and does so concretely (WAV 8 kHz mono plus code text and a link). Combined with the duration limit and parameter ranges, an agent has enough to call it correctly.

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%, and the description largely restates what the schema already documents (wpm 5-40 default 20, frequency 300-1000 default 600). The only added meaning is the relationship between speed, text length, and the 60-second output limit, which is a marginal but real addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Translates text into International Morse code') and specifies the output medium ('WAV audio file, 8 kHz mono'), which implicitly separates it from text-only siblings like text_to_morse. It does not name an alternative explicitly, so differentiation is by output description rather than routing language.

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 context is implied by the audio-output framing, and there is a useful duration workaround ('use a higher speed or a shorter text for more'). However, it never says when to prefer this over text_to_morse or morse_alphabet, and no exclusions or prerequisites are given.

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.