Skip to main content
Glama

Text to Morse code

text_to_morse
Read-onlyIdempotent

Translates text into International Morse code (letters A-Z, digits 0-9 and common punctuation). Returns the code with "." and "-", one space between letters and " / " between words, lists any characters that have no Morse code, and gives a link to the translator on morsecodetranslator.com with the code filled in.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to translate, at most 1000 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: the exact delimiter convention ('.' and '-', one space between letters, ' / ' between words), that unmapped characters are reported back, and that a prefilled external link is returned.

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?

A single sentence that is front-loaded with the purpose and then layers output format, edge-case handling, and the returned link. It is somewhat long and comma-chained, but each clause carries distinct information with no filler.

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?

For a one-parameter, side-effect-free tool with no output schema, the definition covers the input domain, the exact output encoding, the edge case of unmapped characters, and the additional returned link. Nothing an agent needs in order to call it and interpret the result is missing.

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?

There is a single parameter and schema coverage is 100%, with the schema already stating the 1000-character cap and its meaning. The description adds no further semantics beyond what the schema 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.

Purpose4/5

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

The description names a specific verb and resource ('Translates text into International Morse code') and scopes the supported repertoire (A-Z, 0-9, common punctuation). The direction of translation implicitly distinguishes it from morse_to_text, but no sibling is named explicitly, so it falls short of full sibling differentiation.

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 by the direction of conversion; there is no explicit statement of when to pick this over morse_to_text or morse_alphabet, and no prerequisites or exclusions are given. An agent can infer the right choice, but the definition does not do the routing for it.

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.