Skip to main content
Glama

hornmorpho_generate

Generate Ge'ez-script word forms from a consonantal root or lemma by specifying part of speech and HornMorpho features, or return citation forms by default.

Instructions

Generate word forms from a root or lemma in Ge'ez script.

root: a consonantal root such as 'ስብር', or a lemma such as 'ሰበረ' (its root is found automatically). features: a HornMorpho feature structure, for example '[sb=[+p1,+plr]]' for a 1st person plural subject. Run hornmorpho_analyze with include_feats=True on a similar word to see the feature names. pos: 'v' (verb), 'n' (noun), 'vn' (verbal noun), 'cop'. Without pos and features, the citation forms of each derived POS are returned.

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": {
      "root": "<root>"
    },
    "name": "hornmorpho_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
posNo
langNoam
rootYes
featuresNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavior beyond the schema: roots are auto-derived from lemmas, and omitting pos/features returns citation forms for every derived POS. However, it says nothing about error handling for malformed roots or feature strings, unavailability of a POS for a given root, or the cost of enumerating all derived POS, which are the failure modes an agent would hit.

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?

The opening sentence states the purpose, then parameters are explained in the order an agent needs them, with parenthetical examples rather than separate sentences. The prose is tight, though the pos line ('cop') could be expanded slightly since the abbreviation is opaque.

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 values needn't be described, and three of four parameters are well covered. The unexplained lang parameter is a substantive omission: the description frames everything as Ge'ez script, but lang defaults to 'am', leaving an agent unable to tell whether it must set the language for Ge'ez input or whether the default is wrong.

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 largely does: root is explained with examples for both a consonantal root and a lemma, features is given a concrete format ('[sb=[+p1,+plr]]') plus a discovery method, and pos is given an enum ('v', 'n', 'vn', 'cop') that the schema lacks entirely. The one gap is lang, which is never mentioned despite defaulting to 'am'.

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?

The description states a specific verb and resource: generating word forms from a root or lemma in Ge'ez script. It implicitly distinguishes itself from hornmorpho_analyze by describing the inverse direction (generation vs. analysis), though it never explicitly says 'use this instead of analyze when...'. An agent can identify what the tool does without opening the 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?

It gives actionable guidance for the hardest part of invocation: run hornmorpho_analyze with include_feats=True on a similar word to discover valid feature names. It also explains the default path (no pos/features yields citation forms of each derived POS). What's missing is an explicit statement of when to prefer this tool over hornmorpho_analyze or hornmorpho_verb_paradigm, and there is no guidance on unsupported roots or languages.

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