Skip to main content
Glama

geezorg_corpus_search

Search the POS-tagged WIC Amharic news corpus to find real usage examples and part-of-speech tags, returning keyword-in-context lines for each term.

Instructions

Search the POS-tagged Walta Information Center (WIC) Amharic news corpus and return keyword-in-context lines. The tags are inside the text, e.g. ' '. Use it to find real usage examples and part-of-speech tags.

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": {
      "term": "<term>"
    },
    "name": "geezorg_corpus_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes
limitNo
contextNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It helpfully discloses the inline tag format ('<word> <TAG>'), which is real context beyond structured fields, but says nothing about whether matching is exact, substring, or regex, how large the corpus is, or how limit/context shape results — important for a zero-annotation tool. The existence of an output schema offsets the missing return-value explanation.

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 short sentences, front-loaded with the core action and return type before the tag-format note. The tag example earns its place; no filler.

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?

Output schema covers return values and the corpus/tag orientation is conveyed, but for a 3-parameter, zero-annotation, zero-schema-coverage search tool the description leaves the most ambiguous parameter ('context') and the match semantics undefined.

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 compensate and it largely does not. It never explains what 'context' means (window size in characters?), what 'limit' caps, or whether 'term' can itself be a POS tag — despite demonstrating tag syntax in the text, which invites exactly that ambiguity.

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 ('Search') plus a named resource (POS-tagged WIC Amharic news corpus) and the return form (keyword-in-context lines). It is clearly a corpus-text search rather than a lexical lookup, which distinguishes it implicitly from geezorg_lookup, 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?

'Use it to find real usage examples and part-of-speech tags' gives a genuine when-to-use cue. However, there is no guidance on when to prefer geezorg_lookup or geezorg_browse instead, and no statement of exclusions or prerequisites.

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