Skip to main content
Glama

Search the Livonian dictionary

livonian_search
Read-onlyIdempotent

Look a word up in the real Livonian–Estonian–Latvian dictionary and return only attested content, so translations are grounded, not invented.

Search a meaning (in English/Latvian/Estonian) to find the Livonian headword, or a Livonian word to confirm it exists and read its sense, part of speech and examples. See the query and search_language parameter docs for how to phrase a query. By default each match's full inflection table is returned inline, so one call usually suffices; on a broad query only the first N tables expand (the rest are listed as handles to fetch with livonian_get_inflections). Returns Markdown plus the same result as structuredContent matching the declared outputSchema.

Results are cached server-side, so repeating a query is instant and free; a first-time query reaches the live dictionary and calls are rate limited — on a rate-limit error, wait a few seconds and retry instead of re-issuing immediately. Dictionary content is from livonian.tech (CC BY-SA 4.0 — attribute if republished).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA SINGLE content word, not a phrase. Exactly one word per call — even with several candidates or synonyms in mind, search them one at a time ('see', then 'look'), never combined into one query like 'see look'. Drop function words and infinitive markers — search 'to water' as 'water', 'the sea' as 'sea'. The dictionary matches one attested headword, so a multi-word query often returns nothing even when the word exists; search the main word first, then refine. May be Livonian, Latvian, Estonian, or English (e.g. 'jarā', 'away', 'sea'). Matching is bidirectional. An inflected Livonian form (search_language='liv') is resolved to its dictionary lemma automatically when the form is known — the result says so when that happened.
max_formsNoOptional override for how many inflection tables to expand this call (0–12). Raise it to pull more tables in ONE call on a broad query, or set a small value to keep a broad query cheap. On an uncached query each table is fetched sequentially with polite pacing toward the upstream, so a high value on a cold broad query is slow — the bound limits upstream fan-out, not just response size. Omit to use the server's default cap.
include_formsNoWhen true (default), each match's full inflection table is returned INLINE — usable cases/tenses in ONE call, no follow-up livonian_get_inflections. Set false to get just the headword handles + glosses: a cheap way to SCREEN several candidate words or synonyms (which exist? which sense?) before spending forms on the one you pick. Bounded by a per-search cap — use max_forms to raise or lower it for this call.
search_languageNoLanguage your query word is in — selects which language the search matches against: 'eng' (default), 'liv', 'lat', or 'est'. For English→Livonian translation, keep 'eng'. Glosses are in English.eng

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYesFalse when nothing matched.
queryYes
sourceNoErnštreits, Valts (ed. in chief), Viitso, Tiit-Rein, Vāvere, Signis, Damberg, Pētõr, Kurpniece, Milda, Balodis, Uldis, Tuisk, Tuuli, Kūla, Gita, Tomingas, Marili, Soosaar Sven-Erik, Sedláčková, Anna & Jurgenovskis, Toms. 2024. Livonian lexicographic database. Riga: University of Latvia Livonian Institute. https://livonian.tech/ (CC BY-SA 4.0)
entriesNoStructured dictionary entries: headword, pronunciation, part of speech, paradigm anchors, and senses with example sentences.
handlesNo
languageYes
resolved_fromNoThe original inflected query when search_method='lemma_index'; empty on a direct match.
search_methodNoHow the match was found: 'direct' = the query itself matched; 'lemma_index' = the query was an inflected Livonian form, resolved to its dictionary lemma via the cached paradigm index and re-searched.direct
resolved_lemmaNoThe dictionary lemma actually searched when search_method='lemma_index'; empty on a direct match.
forms_truncatedNoHow many handles did NOT get an inline table because the per-search cap was reached. Refine the query or call livonian_get_inflections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / include_forms / description
      Previous value: -"When true (default), each match's full inflection table is returned INLINE — usable cases/tenses in ONE call, no follow-up get_inflections. Set false to get just the headword handles + glosses: a cheap way to SCREEN several candidate words or synonyms (which exist? which sense?) before spending forms on the one you pick. Bounded by a per-search cap — use max_forms to raise or lower it for this call."New value: +"When true (default), each match's full inflection table is returned INLINE — usable cases/tenses in ONE call, no follow-up livonian_get_inflections. Set false to get just the headword handles + glosses: a cheap way to SCREEN several candidate words or synonyms (which exist? which sense?) before spending forms on the one you pick. Bounded by a per-search cap — use max_forms to raise or lower it for this call."
    • changedInput schema / title
      Previous value: -"search_livonianArguments"New value: +"livonian_searchArguments"
    • changedOutput schema / $defs / Entry / description
      Previous value: -"One dictionary entry (one upstream result card): the headword with its\npronunciation, part of speech, paradigm anchors, and senses.\n\n``entry_id`` + ``word_class`` are the same anchors carried by an\n:class:`InflectionHandle` — feed them to ``get_inflections`` for the full paradigm.\nEvery field except ``headword``/``gloss`` defaults, so a card missing a\npronunciation, type code, or senses still validates."New value: +"One dictionary entry (one upstream result card): the headword with its\npronunciation, part of speech, paradigm anchors, and senses.\n\n``entry_id`` + ``word_class`` are the same anchors carried by an\n:class:`InflectionHandle` — feed them to ``livonian_get_inflections`` for the full paradigm.\nEvery field except ``headword``/``gloss`` defaults, so a card missing a\npronunciation, type code, or senses still validates."
    • changedOutput schema / $defs / InflectionHandle / description
      Previous value: -"A reliable, structured anchor for fetching a full paradigm. Feed\n``entry_id`` + ``word_class`` to ``get_inflections`` — or ask ``search`` to\ninclude the table inline (``forms``)."New value: +"A reliable, structured anchor for fetching a full paradigm. Feed\n``entry_id`` + ``word_class`` to ``livonian_get_inflections`` — or ask ``search`` to\ninclude the table inline (``forms``)."
    • changedOutput schema / properties / forms_truncated / description
      Previous value: -"How many handles did NOT get an inline table because the per-search cap was reached. Refine the query or call get_inflections."New value: +"How many handles did NOT get an inline table because the per-search cap was reached. Refine the query or call livonian_get_inflections."
  2. First observed

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), yet the description adds substantial behavioral context beyond them: server-side caching, rate limiting with retry advice, truncation of inflection tables to handles on broad queries, and CC BY-SA licensing/attribution. Return shape (Markdown plus structuredContent) is also disclosed.

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 action and grounding rationale, and each sentence carries real information (default behavior, screening workflow, caching, licensing). Slightly long, and the parenthetical licensing/attribution note is tangential to tool invocation, but there is no filler.

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?

With an output schema declared, the description need not detail return values, yet it still tells the agent the format and that one call usually suffices. Combined with the caching/rate-limit guidance and sibling routing, an agent has everything needed to call this correctly on the first attempt.

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 cross-references to the query/search_language docs and explains the default inline-table behavior and its interaction with max_forms and include_forms, which the schema states only per-parameter. It stops short of restating query syntax itself, deferring to 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 and resource ('Look a word up in the real Livonian–Estonian–Latvian dictionary') and defines the bidirectional scope: meaning→Livonian headword, or Livonian word→sense/POS/examples. It also distinguishes itself from the sibling livonian_get_inflections by naming it as the fallback for non-expanded tables.

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 concrete when-to-use guidance, including the screening workflow ('set include_forms false ... to SCREEN several candidate words ... before spending forms on the one you pick') and the alternative for fetching remaining tables (livonian_get_inflections). It also covers the retry case on rate-limit errors.

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