Skip to main content
Glama

Look an Old English word up

anglo_search
Read-onlyIdempotent

Look an Old English word up on Wiktionary and return its senses plus full declension/conjugation tables — attested content, not invented. Any form of the word works; an inflected query is resolved to its lemma automatically via previously cached paradigms and the result notes the resolution. With search_language='eng' the query is a modern English word instead: the result lists its per-sense Old English equivalents (the translations block) plus their expanded entries. Returns Markdown plus the same result as structuredContent matching the declared outputSchema.

Results are cached server-side; first-time queries reach the live upstream politely and calls are rate limited — on a rate-limit error, wait a few seconds and retry. Content is from en.wiktionary.org (CC BY-SA 4.0 — attribute and share alike if republished).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe word to look up, in the language search_language names. Old English (default): a SINGLE Old English word, any form — an inflected form ('bindaþ') is resolved to its lemma ('bindan') automatically via cached paradigms, and the result says so; the special letters are optional once a paradigm is cached ('thing' finds þing, 'waeter' finds wæter). English (search_language='eng'): the English word whose Old English equivalents you want — multiword entries like 'apple tree' work.
max_formsNoOptional override for how many inflection tables to expand this call (0–12). On an uncached query each table is one politely paced upstream fetch, so high values on cold queries are slow. Omit for the server default.
include_formsNoWhen true (default), each match's full declension/conjugation table is returned INLINE — usable cases/tenses (nouns, the adjectives' strong/weak family, the verbs' moods, the pronouns' dual) in ONE call, no follow-up anglo_get_inflections. Set false for a cheap screen of which entries exist. Bounded by a per-search cap — use max_forms to adjust per call. For eng queries this governs the expanded Old English entries; the per-sense translations list itself is always returned.
search_languageNoLanguage the query word is in: 'ang' (default) looks the Old English word up directly; 'eng' finds the Old English equivalents of a modern English word (per-sense, from Wiktionary's translation tables) and returns their full entries. Glosses are in modern English either way.ang

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYesFalse when nothing matched. For an eng query, True means Old English translations were found — entries may still be empty when none of them could be expanded (see translations).
queryYes
sourceNoWiktionary, the free dictionary (en.wiktionary.org), Old English entries. Wikimedia Foundation. Text available under CC BY-SA 4.0; attribution and share-alike required when republishing. (CC BY-SA 4.0)
entriesNo
handlesNo
languageYes
translationsNoPopulated only for eng queries (always [] for ang): the Old English terms each English sense translates to, in sense order. Entries/handles below are the expanded dictionary entries of those terms.
resolved_fromNoThe original inflected query when resolved; else empty. ang queries only — always empty for eng results.
search_methodNoHow the match was found: 'direct' = the query itself matched; 'lemma_index' = an inflected form resolved via a previously cached paradigm; 'translations' = an English query resolved via Wiktionary translation tables.direct
resolved_lemmaNoThe lemma actually searched when resolved; else empty. ang queries only — always empty for eng results.
forms_truncatedNoHow many handles did NOT get an inline table because the per-search cap was reached.
translations_truncatedNoHow many distinct translated lemmas were NOT expanded into entries because the per-search expansion cap was reached (they still appear under translations).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly/idempotent/non-destructive/openWorld), and the description adds substantial beyond-schema behavior: server-side caching, politely paced live upstream fetches, rate limiting with retry advice, automatic lemma resolution via cached paradigms, and licensing/provenance. This is exactly the extra context annotations cannot carry.

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 core purpose, then modes, then caching/rate-limit notes; every sentence carries information. Slightly verbose and somewhat duplicative of the schema's own parameter descriptions, but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search with an output schema, the description covers return format (Markdown plus structuredContent matching outputSchema), mode behavior, caching, rate limits, and provenance. Nothing an agent needs to invoke it correctly is 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 100%, so the baseline is 3, but the description adds real meaning: inflected queries resolve to a lemma, special letters become optional once paradigms are cached, multiword 'eng' queries work, and max_forms trades upstream fetches for latency. It stops short of full per-parameter detail but clearly exceeds the schema.

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?

States a specific verb (look up), resource (an Old English word on Wiktionary), and output (senses plus full declension/conjugation tables), and explicitly contrasts with the sibling anglo_get_inflections. An agent can distinguish it from anglo_get_inflections and anglo_romanize without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit mode selection (search_language='ang' vs 'eng'), states that include_forms=true avoids a follow-up anglo_get_inflections call, tells the agent to use include_forms=false for a cheap screen, and prescribes the retry behavior on rate-limit errors. When-to-use and alternatives are both covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources