Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Morse code translator: text to Morse and back

text_morse
Read-only

Translate text to international Morse code (letters separated by spaces, words by /) or Morse code back to text; the direction is detected automatically or set with mode. Letters, digits and common punctuation are supported; anything else is reported, not guessed. Use for puzzles, radio practice and fun messages. Example: text=SOS help. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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_morse"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoauto (default), encode or decode
textYesText, or Morse code made of . - spaces and /

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses the charging model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free) and explains that repeats are not free, which is the business justification for idempotentHint=false. It also states that unsupported characters are 'reported, not guessed', a useful error-behavior detail not present in structured fields.

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?

Direction and format conventions are front-loaded, then supported characters, then use cases and pricing. The pricing sentence is long and slightly crowds out the functional content, but every clause carries information.

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 no output schema, the description still conveys input/output conventions and unsupported-character handling, and annotations cover the safety profile. Only the exact shape of an error report is left implicit, which is a minor gap for a two-parameter tool.

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 already 100%, so both parameters are documented structurally, but the description still adds meaning: the spacing convention (letters space-separated, words by '/') and the supported character set, which matter when constructing the text argument. The allowed mode values are left to the schema.

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 names a specific transformation (text ↔ international Morse code), states both directions and that direction is auto-detected or forced by mode. This clearly separates it from siblings such as text_caesar or case, which also transform strings but with different rules.

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

Usage Guidelines4/5

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

It gives concrete usage contexts ('puzzles, radio practice and fun messages') and a worked example ('text=SOS help'), which is enough for an agent to recognize the intended scenario. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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.