Skip to main content
Glama

hornmorpho_analyze_sentence

Analyzes tokenized Amharic or Tigrinya sentences to return CoNLL-U annotations with lemmas, UPOS tags, features, and morpheme segmentation, splitting clitics into separate tokens.

Instructions

Analyze a tokenized sentence (words separated by spaces, punctuation split off). Returns a CoNLL-U annotation with lemmas, UPOS, features and morpheme segmentation (clitics become separate tokens). Full dependency trees are not predicted. lang: am | ti.

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": {
      "sentence": "<sentence>"
    },
    "name": "hornmorpho_analyze_sentence"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoam
sentenceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does a fair job: it discloses the output format (CoNLL-U), the clitic-splitting behavior, and the negative constraint that dependency trees are not predicted. What is missing is any note on failure modes, language-coverage limits, or what happens with untokenized input.

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?

Three compact sentences with the resource and input contract front-loaded and the scope caveat last. The terse 'lang: am | ti' fragment is efficient rather than sloppy, and no sentence is filler.

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 two-parameter read-only analysis tool with an output schema present, the description covers input format, language options, and output nature. Given an output schema exists, the restatement of return contents is harmless redundancy, and nothing an agent needs to call it correctly appears to be missing.

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%, so the description has to compensate, and it does for both parameters: 'sentence' is defined as pre-tokenized words separated by spaces with punctuation split off, and 'lang' is given its allowed values am | ti, which the schema does not enumerate. It does not expand those codes to language names or note the default of 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 names a specific verb and resource ('Analyze a tokenized sentence') and spells out the output shape (CoNLL-U with lemmas, UPOS, features, morpheme segmentation). It also states a scope limit ('Full dependency trees are not predicted'), which helps separate it from a full parser. It stops short of naming the sibling hornmorpho_analyze, so the distinction from word-level analysis is left implicit.

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 precondition is stated clearly: input must already be tokenized with spaces, and punctuation split off. That tells the agent what to prepare but not when to pick this over hornmorpho_analyze or hornmorpho_generate. Usage is implied by the input shape rather than made explicit.

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