Skip to main content
Glama

geezorg_verb_paradigm

Returns the conjugation table for an Amharic verb from the Armbruster list, including perfect, contingent, imperfect, jussive, imperative, gerund, infinitive, participle, and translation.

Instructions

Return the conjugation table of an Amharic verb from the Armbruster list: simple and compound perfect, contingent, imperfect, jussive, imperative, gerund, infinitive, participle, translation, verb type. Give the 3rd person masculine perfect in Ge'ez script (e.g. 'ሰበረ'), or an English translation (e.g. 'break'). Gemination is marked with U+135F.

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": {
      "verb": "<verb>"
    },
    "name": "geezorg_verb_paradigm"
  }
}

Input Schema

NameRequiredDescriptionDefault
verbYes
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 usefully discloses the data source (Armbruster list) and the orthographic convention that gemination is marked with U+135F. It is silent on failure behavior when a verb is not found, on whether multiple matches can be returned, and on what 'limit' constrains — gaps that matter for an unannotated tool.

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?

Two sentences, front-loaded with the purpose, then the input format and a notation caveat. The enumeration of conjugation forms is long but functional, since it tells the agent what the table contains; nothing is padded or redundant.

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 explained, and the input format is well covered. Completeness falls short on the unexplained 'limit' parameter and on what happens with ambiguous or unmatched verbs, which an agent would need before calling confidently.

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

Parameters3/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 supply all parameter meaning. It does an excellent job for 'verb' by specifying accepted input forms and giving script and translation examples, but it never mentions the 'limit' parameter (default 5), leaving one of two parameters entirely undefined in both schema and description.

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 names a specific verb and resource ('Return the conjugation table of an Amharic verb from the Armbruster list') and enumerates the forms returned (perfect, contingent, imperfect, jussive, imperative, gerund, infinitive, participle, translation, verb type). It implicitly separates itself from the morphological siblings by naming its source corpus, but never explicitly distinguishes itself from hornmorpho_analyze or hornmorpho_generate.

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?

The description gives concrete input guidance — supply the 3rd person masculine perfect in Ge'ez script ('ሰበረ') or an English translation ('break') — which tells the agent how to call it. It offers no when-to-use versus when-not guidance and no alternatives among the sibling lookup/morphology tools.

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