Skip to main content
Glama

afrim_lookup

Search Amharic words and Ethiopian personal names by Ge'ez or romanized spelling to verify existence and correct spelling; restrict results to dictionary or names.

Instructions

Search the Amharic wordlist (~340k inflected word forms crawled from the web) and the Ethiopian personal-names list. Use it to check that an Amharic word exists and how it is spelled; there are no glosses. A Ge'ez-script query (e.g. 'ኢትዮጵያ') searches the words; a romanised query (e.g. 'aityoPya') searches the keyboard spellings. Ranking: exact, case-insensitive (romanised only), prefix, then substring. dataset: 'dictionary' or 'names' to restrict the search.

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": "afrim_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
datasetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses the data sources, that results are ranked exact > case-insensitive (romanised only) > prefix > substring, the per-dataset restriction, and the absence of glosses. It does not state that the operation is read-only or mention any rate/size limits, but the read-only nature is strongly implied by 'search' and 'check'.

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?

Front-loaded with the resource and its size, then usage, then query-type routing, then ranking, then dataset values. Nearly every sentence adds information; the 'no glosses' caveat and the examples are load-bearing rather than 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?

An output schema exists, so return values need no explanation, and the description covers the two non-trivial knobs (query script, dataset) plus result ordering. The only real gap is the unexplained `limit` parameter and no hint about result volume.

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 coverage is 0%, so description must compensate. It does well for `query` (script-dependent interpretation with concrete examples) and `dataset` (explicit values 'dictionary' or 'names'), but `limit` is never mentioned, leaving one of three parameters undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (search) and concrete resources (the ~340k-form Amharic wordlist and the Ethiopian personal-names list), and explicitly bounds the scope with 'there are no glosses'. That last clause distinguishes it from a dictionary/translation tool without needing to name siblings.

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 a clear use case: 'check that an Amharic word exists and how it is spelled'. It also tells the agent which kind of query goes to which index (Ge'ez script vs romanised keyboard spellings), which is real routing guidance. It stops short of naming an alternative tool or stating when not to use it.

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