SandiMorse

Morse code practice

morse_practice

Read-onlyIdempotent

Returns ten Morse code practice questions with their answers: letter to code, code to letter, words, listening and mixed rounds. Listening questions carry the code to play. Includes a link to the SandiMorse practice page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "morse_practice"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Round type: letter-code, code-letter, words, listen or mixed (default).
`round`	No	Question set number from 1; a different number gives a different set of ten questions. Default 1.
`language`	No	Language of the answer and of the page the link opens: id for Indonesian or en for English. Default id.

Output Schema

Name	Required	Description	Default
`item`	Yes
`view`	Yes
`language`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds that listening questions carry the code to play and that a link to the SandiMorse practice page is included, but says nothing about pagination, determinism across calls, or limits beyond what the schema notes.

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 compact sentences with the core output front-loaded and the ancillary link detail placed last. Little wasted wording, though the phrase 'letter to code, code to letter' is slightly loose compared to the enum values.

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, full annotation coverage, and fully documented parameters, the description only needs to orient the agent, and it does so: it states the count of questions, the round vocabulary, and the listening-code behavior. Missing only comparison to sibling tools and any note on determinism of the round number.

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 all three parameters (mode, round, language) are documented with enums and defaults, so the baseline is 3. The description's mention of round types mirrors the mode enum and adds no syntax, numbering, or language behavior beyond what the schema already states.

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?

The description gives a concrete verb and resource: it returns ten Morse code practice questions with answers, and it enumerates the round types (letter-to-code, code-to-letter, words, listening, mixed). This is clearly distinct from siblings like morse_chart or translate_morse, though it never names or contrasts them explicitly.

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 only implied: the tool is for practice, and the round types hint at when each mode applies. There is no explicit when-to-use/when-not-to-use guidance and no mention of the alternative tools an agent might pick instead (e.g., translate_morse for a single conversion).

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

All SandiMorse tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.