Skip to main content
Glama

afrim_keystrokes

Convert Ge'ez-script text into afrim keyboard keystrokes, returning the shortest key sequence and a per-character breakdown for typing Amharic, Tigrinya, or Ge'ez text.

Instructions

Give the keystrokes that type Ge'ez-script text with an afrim keyboard layout (the reverse of afrim_transliterate), e.g. ኢትዮጵያ -> 'aityoPya'. Each character uses the shortest key sequence. Returns the keystroke string and a per-character breakdown. scheme: am | gez | ethiopic | geezime.

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

Input Schema

NameRequiredDescriptionDefault
textYes
schemeNoam

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, the description carries the full burden and does reasonably well: it discloses the algorithm trait ('each character uses the shortest key sequence') and the return shape (keystroke string plus per-character breakdown). It does not mention error behavior for invalid schemes or non-Ge'ez input, which is a minor gap.

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 purpose, then the example, then the return shape, then the scheme list — a logical order with no filler. The trailing 'scheme:' fragment is terse but functional.

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 needn't be re-explained, and the description still summarizes them. Combined with the example and scheme enumeration, an agent has enough to call the tool correctly; only edge-case behavior is unaddressed.

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 0% and the schema has no enum, so the description must compensate — and it does by enumerating valid scheme values ('am | gez | ethiopic | geezime') and clarifying that 'text' is Ge'ez-script input. It does not state the default scheme or what happens with an unrecognized scheme value.

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 ('give the keystrokes that type Ge'ez-script text'), positions it precisely as the reverse of afrim_transliterate, and includes a concrete example (ኢትዮጵያ -> 'aityoPya'). An agent can distinguish it from the transliterate sibling without opening either schema.

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?

The 'reverse of afrim_transliterate' framing gives clear directional context for choosing between the two tools, and the example makes the input/output orientation unambiguous. It stops short of an explicit when-to-use/when-not-to-use statement or naming other alternatives.

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