Skip to main content
Glama

hornmorpho_phonetic

Transliterates Ge'ez-script words into phonetic readings, revealing gemination and unwritten epenthetic vowels so users can distinguish distinct pronunciations.

Instructions

Phonetic transliteration of a Ge'ez script word, showing gemination and the epenthetic vowels the script does not write. One entry per distinct reading (e.g. ሰበረ -> səbbərə or səbərə).

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": {
      "word": "<word>"
    },
    "name": "hornmorpho_phonetic"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoam
wordYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the most important behavioral trait: the output is one-to-many, with a separate entry per distinct reading. It also explains what phonetic information is surfaced (gemination, unwritten epenthetic vowels). It does not state that the operation is read-only or how many readings are typically returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the core definition first, then a worked example that makes the multi-reading behavior concrete. Every clause adds information, and the highest-value detail (one entry per reading) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 structure need not be re-explained, and the description covers output cardinality well. The clear gap is the undocumented 'lang' parameter, which an agent would have to guess at for a non-Amharic word.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 explain both parameters. It clarifies that 'word' is a Ge'ez script word, but the 'lang' parameter (default 'am') is never mentioned at all, leaving its purpose and accepted values undocumented anywhere.

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: phonetic transliteration of a Ge'ez script word, with a concrete example (ሰበረ -> səbbərə or səbərə). The 'one entry per distinct reading' clause separates it from a plain morphological analyzer like hornmorpho_analyze, though no sibling is named explicitly.

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 implied by the example and the phrase 'the epenthetic vowels the script does not write' – an agent can infer this is for turning unvocalized script into phonetics. There is no explicit when-to-use or when-not guidance, and no mention of how this differs from transliteration siblings such as afrim_transliterate.

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