Skip to main content
Glama

hornmorpho_analyze

Analyze Ge'ez-script word to return lemma, root, part of speech, segmentation, UD/UniMorph features, transliteration, and morpheme details for Amharic, Tigrinya, Oromo, or Tigre; guess unknown words.

Instructions

Analyze one word in Ge'ez script (e.g. 'የቤታችን').

Returns every analysis, with its lemma, root, part of speech, segmentation ('seg', stem between < >), Universal Dependencies features ('udfeats'), UniMorph tags ('um'), a transliteration ('translit', gemination shown) and per-morpheme details. guess=True guesses analyses for unknown words. include_feats=True also returns HornMorpho's full feature structure, which shows the feature names that hornmorpho_generate accepts. lang: am | ti | om | tig.

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

Input Schema

NameRequiredDescriptionDefault
langNoam
wordYes
guessNo
include_featsNo

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 burden and does well: it discloses that all analyses are returned with lemma, root, POS, segmentation, UD features, UniMorph tags and transliteration, and explains what each optional flag changes about the output. It does not state what happens when a word is unknown and guess is false (empty result vs. error), which is the main remaining behavioral 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 action and an example, followed by the return payload and then per-flag guidance. The field enumeration is long but each item is informative; minor tightening is possible around the segmentation/stem parenthetical.

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 4-parameter analysis tool with an output schema, the definition covers inputs, output fields and flag semantics thoroughly. Remaining gaps are edge-case behavior (no-analysis case, invalid script input) rather than core calling information, and the output schema already documents return structure.

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%, yet the description explains all four parameters: word (Ge'ez script, with an example), lang (allowed values am | ti | om | tig), guess (guesses analyses for unknown words) and include_feats (adds HornMorpho's full feature structure). It omits the default values and any input normalization rules for the script, so it adds strong but not exhaustive meaning.

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 ('Analyze one word in Ge'ez script') with a concrete example input. The emphasis on 'one word' implicitly distinguishes it from hornmorpho_analyze_sentence, and the reference to hornmorpho_generate makes the analyze/generate pairing explicit.

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?

Gives conditional guidance for the optional flags: guess=True for unknown words, include_feats=True when the caller needs the feature names that hornmorpho_generate accepts. It does not explicitly state when to prefer hornmorpho_analyze_sentence or hornmorpho_phonetic instead, so alternatives are only partly addressed.

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