Skip to main content
Glama

geezorg_lookup

Search Ge'ez script headwords or English glosses in Ethiopic dictionaries, ranked by exact, prefix, whole-word and substring matches, with optional language and dataset filters.

Instructions

Look up a word in the dictionaries.

A query in Ge'ez script (e.g. 'ቤት') searches headwords. A Latin-script query (e.g. 'house') searches the English glosses. Results are ranked exact match, then prefix, then whole word, then substring. lang: am | ti | gez filters by language. dataset: a dataset id from geezorg_list_datasets.

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": {
      "query": "<query>"
    },
    "name": "geezorg_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
limitNo
queryYes
datasetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden; it does disclose the non-obvious ranking order (exact, prefix, whole word, substring) and the language/dataset scoping, which is real behavioral value. It says nothing about result limits or truncation behavior, whether a missing match errors or returns empty, or the shape of results (though an output schema exists).

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?

It is short and front-loaded, leading with the core action before query semantics and filters. The line breaks split sentences awkwardly ("...Latin-script / query...") and each parameter hint is compressed into a single terse line, but 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 4-parameter read-only lookup with an output schema, the description covers the essential decision inputs: how to phrase the query, how to restrict language, and where dataset ids come from. The gaps (limit behavior, empty-result handling) are minor, and the existence of an output schema removes any obligation to describe return values.

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: query semantics (script decides headword vs gloss search), the lang vocabulary (am | ti | gez), and the provenance of dataset are all explained beyond the bare property names. Only 'limit' is left unexplained, though its default of 20 in the schema makes it self-evident.

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 first line gives a specific verb and resource ("look up a word in the dictionaries"), and the following sentences explain that the script of the query determines whether headwords or English glosses are searched, which is genuinely differentiating. It does not, however, contrast itself with siblings like geezorg_corpus_search or afrim_lookup, so an agent must still infer which lookup tool fits which need.

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?

Usage is implied rather than stated: the script-routing rule tells you how to phrase a query, and the dataset field is explicitly tied to geezorg_list_datasets, which is a useful pointer. There is no explicit when-to-use/when-not guidance versus the corpus or browse siblings, and no statement about what happens when no match is found.

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