SandiMorse

Encode a scout code

encode_scout_code

Read-onlyIdempotent

Writes a message in one of the scout codes on SandiMorse: kotak 1, 2 and 3, rumput, semaphore, angka, koordinat, Merah Putih, Polybius, AZ (Atbash), AN (ROT13), kimia, jam, AND, Napoleon or ular. Returns the coded text, or a picture for the drawn codes, with the key used and a link to the SandiMorse page with the same input.

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": {
      "code": "<code>",
      "text": "<text>"
    },
    "name": "encode_scout_code"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	Code to write in.
`hour`	No	Hour of the letter A in jam, 0 to 23. Default 8.
`step`	No	Step between letters: a number for angka (default 1) or minutes for jam (default 5).
`text`	Yes	The message to encode. Drawn codes (kotak, rumput, semaphore) take up to 120 characters, the others up to 300.
`start`	No	Number for the letter A in angka. Default 1.
`style`	No	Placement of AND in the AND code: syllable puts it after a consonant before a vowel and at the end of a word, every puts it between all letters. Default syllable.
`width`	No	Letters per row in napoleon (default 6) or ular (default 4), 2 to 30.
`minute`	No	Minute of the letter A in jam, 0 to 59. Default 0.
`reading`	No	Reading order of ular: snake reads rows back and forth, column reads top to bottom. Default snake.
`compress`	No	Kimia: write equal neighbouring symbols with a number (HH as H2). Default true.
`language`	No	Language of the answer and of the page the link opens: id for Indonesian or en for English. Default id.
`top_word`	No	Column key word of koordinat: 5 different letters A to Z. Both key words are needed for a custom key.
`left_word`	No	Row key word of koordinat: 5 different letters A to Z.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is well covered and 'Writes' here clearly means encoding, not database mutation. The description adds that a picture is returned for drawn codes together with the key used and a SandiMorse link, which is genuine extra context, but it says nothing about failure modes such as invalid characters for a given code.

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 front-loaded sentences: the first establishes the action and the domain, the second covers the return. The long code enumeration duplicates the enum but is arguably what an agent needs to match a user's named cipher, so the length mostly earns its place.

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?

For a 13-parameter tool, the description is appropriately lean because the schema carries per-parameter detail at 100% coverage, an output schema exists to explain returns, and annotations carry the safety profile. The remaining gap is that the conditional coupling between codes and their tuning parameters is only discoverable by reading each schema field.

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 all thirteen parameters are documented at the source; the description adds only the human-readable expansion of the abbreviation enums (AZ = Atbash, AN = ROT13) and a restatement of the 120/300 character split. It says nothing about the tuning parameters (hour, step, width, style, reading) or that the two koordinat keywords must be supplied together, so baseline 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?

States a specific verb and resource ('Writes a message in one of the scout codes') and enumerates all sixteen supported codes, so an agent knows exactly what the tool produces. It never names the encode/decode counterpart, so routing against decode_scout_code is left to the reader even though the verb makes it fairly obvious.

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 encoding verb and the scope list; there is no explicit statement of when to pick this over decode_scout_code or list_codes, and no prerequisites or exclusions. An agent can infer the direction of the operation, but nothing tells it the boundary conditions.

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.