Skip to main content
Glama

afrim_transliterate

Convert romanised keyboard input into Ge'ez script with afrim-compatible layouts for Amharic and Tigrinya, resolving vowel forms, capitals, and punctuation and returning a per-word breakdown.

Instructions

Convert romanised keyboard input to Ge'ez script, as the afrim input method types it (greedy longest key match). The 'am' layout is SERA-like and case-sensitive: consonant + e u i a ie o (ሰ=se ሱ=su ሲ=si ሳ=sa ሴ=sie ሶ=so), a bare consonant is the 6th form (ስ=s), capitals are other consonants (ጠ=Te ጨ=Ce ጰ=Pe ሸ=xe ቀ=qe), and a vowel standing alone takes an 'a' prefix (አ=ae ኢ=ai እ=a). Examples: 'selam' -> ሰላም, 'aityoPya' -> ኢትዮጵያ, 'biet' -> ቤት. Punctuation: ':' -> ፡, '::' or '.' -> ።, ',' -> ፣. Use afrim_keystrokes to find the keys for a Ge'ez word.

scheme: am (default) | gez | ethiopic | geezime. use_wordlist: with 'am', a word that is in the Amharic wordlist or the names list is replaced by its listed spelling (useful where the keyboard map is ambiguous). Each word reports whether it was found there. Returns the text and a per-word breakdown.

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

Input Schema

NameRequiredDescriptionDefault
textYes
schemeNoam
use_wordlistNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does so well: it discloses greedy longest-match resolution, case sensitivity, the sixth-form rule for bare consonants, vowel-prefix behavior, punctuation mappings, and that wordlist hits are substituted and reported per word. It stops short of stating what happens on unmapped input, whether conversion is lossless, or how ambiguity is resolved when no wordlist entry exists.

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 the core transformation before the rule detail, and every sentence carries mapping or usage information. It is dense but somewhat over-packed, embedding both inline key examples and full-word examples that partially repeat the same rule.

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?

An output schema exists, so return values need not be spelled out, and the description still notes that a per-word breakdown is included. For a three-parameter transliteration tool with nuanced, case-sensitive rules this is nearly complete, missing only edge-case behavior for unmapped characters and scheme differentiation.

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 description coverage is 0%, so the description must compensate, and it does for most parameters: it enumerates the scheme values (am default, gez, ethiopic, geezime) that the schema does not constrain with an enum, and describes the practical effect of use_wordlist plus the per-word reporting it triggers. It never clarifies whether gez/ethiopic/geezime are aliases or distinct layouts, and it does not name the 'text' parameter's expected input format explicitly.

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?

States a specific verb and resource ('Convert romanised keyboard input to Ge'ez script') and pins the exact behavior to the afrim input method, which separates it from siblings like afrim_keystrokes or afrim_lookup without opening their schemas. The accompanying mapping examples make the transformation the tool performs concrete.

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?

Explicitly routes the inverse task to afrim_keystrokes ('Use afrim_keystrokes to find the keys for a Ge'ez word') and explains when to enable use_wordlist (where the keyboard map is ambiguous). It does not contrast the four scheme choices or say when a scheme other than the default 'am' is appropriate, leaving that inference to the agent.

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