Skip to main content
Glama

hub

by com.valksor
OverviewDiscussionsAdmin

Look a Proto-Scythian word up

scythian_search
Read-onlyIdempotent

Look a Proto-Scythian lemma up on Wiktionary and return its senses plus its full descendants payload — the reconstructed etymology and the reflex tree down to Ossetian and Khotanese, attested scholarship, not invention. Plain ASCII spellings are folded to the reconstruction's diacritics and the result notes the resolution. With search_language='eng' the query is an English word instead: the result lists the lemmas whose glosses match it (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. Scythian (default): a SINGLE Proto-Scythian lemma — plain ASCII works ('tigri' finds *tiɣri: macrons and carons are folded, and ɣ→g, δ→d, β→b, ə→e, θ→t or th), with or without the reconstruction asterisk. English (search_language='eng'): the English word whose Proto-Scythian equivalents you want — matched against every entry's glosses.
max_formsNoOptional override for how many descendants payloads to expand this call (0–12). On an uncached query each payload 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 descendants payload — etymology, glosses and the reflex tree down to Ossetian and Khotanese — is returned INLINE in ONE call, no follow-up scythian_get_descendants. 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 entries; the matched-lemmas list itself is always returned.
search_languageNoLanguage the query word is in: 'xsc' (default) looks the Proto-Scythian lemma up directly; 'eng' finds the lemmas whose English glosses match the query (the local gloss index — reconstructed languages have no translation tables) and returns their full entries. Glosses are in English either way.xsc

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYesFalse when nothing matched. For an eng query, True means the gloss index named Proto-Scythian lemmas — entries may still be empty when none of them could be expanded (see translations).
queryYes
sourceNoWiktionary, the free dictionary (en.wiktionary.org), Proto-Scythian reconstruction 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 xsc): the Proto-Scythian lemmas whose glosses match the query. Entries/handles below are the expanded dictionary entries of those lemmas.
resolved_fromNoThe original query when resolved via the index; else empty. xsc queries only — always empty for eng results.
search_methodNoHow the match was found: 'direct' = the query itself matched; 'lemma_index' = an ASCII/diacritic-folded spelling resolved via the reverse index; 'translations' = an English query resolved via the local gloss index.direct
resolved_lemmaNoThe lemma actually searched when resolved; else empty. xsc queries only — always empty for eng results.
forms_truncatedNoHow many handles did NOT get an inline descendants payload because the per-search cap was reached.
translations_truncatedNoHow many distinct matched 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
  2. Removed
  3. Changed6 schema fields changed
    • changedInput schema / properties / include_forms / description
      Previous value: -"When true (default), each match's full descendants payload — etymology, glosses and the reflex tree down to Ossetian and Khotanese — is returned INLINE in ONE call, no follow-up get_descendants_scythian. 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 entries; the matched-lemmas list itself is always returned."New value: +"When true (default), each match's full descendants payload — etymology, glosses and the reflex tree down to Ossetian and Khotanese — is returned INLINE in ONE call, no follow-up scythian_get_descendants. 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 entries; the matched-lemmas list itself is always returned."
    • changedInput schema / title
      Previous value: -"search_scythianArguments"New value: +"scythian_searchArguments"
    • changedOutput schema / $defs / DescendantsHandle / description
      Previous value: -"A structured anchor for fetching one entry's descendants: feed ``entry_id``\n(the bare lemma) + ``word_class`` (the POS section) to\n``get_descendants_scythian`` — or ask ``search`` to include the tree inline\n(``forms``)."New value: +"A structured anchor for fetching one entry's descendants: feed ``entry_id``\n(the bare lemma) + ``word_class`` (the POS section) to\n``scythian_get_descendants`` — or ask ``search`` to include the tree inline\n(``forms``)."
    • changedOutput schema / $defs / Entry / properties / entry_id / description
      Previous value: -"Bare lemma — feed to get_descendants_scythian."New value: +"Bare lemma — feed to scythian_get_descendants."
    • changedOutput schema / $defs / Entry / properties / word_class / description
      Previous value: -"POS section — feed to get_descendants_scythian."New value: +"POS section — feed to scythian_get_descendants."
    • changedOutput schema / $defs / TranslationTerm / description
      Previous value: -"One Proto-Scythian lemma the gloss index offers for an English query.\n``word`` is the bare lemma (what an ``eng`` search re-searches and what\n``get_descendants_scythian`` needs)."New value: +"One Proto-Scythian lemma the gloss index offers for an English query.\n``word`` is the bare lemma (what an ``eng`` search re-searches and what\n``scythian_get_descendants`` needs)."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations: it discloses server-side caching, politely paced live upstream fetches, rate limiting with an explicit retry-advice ('wait a few seconds and retry'), and the CC BY-SA 4.0 attribution obligation. It also explains the ASCII-to-diacritic folding behavior and that the result reports the resolution.

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-loads the core action and payload in the first sentence, then layers the eng-mode variant, output format, caching/rate-limit caveats, and license in short paragraphs. A few points (eng-mode lookup, descendants payload) restate schema material, but nothing is truly wasted.

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 present, the description needn't explain return values, and annotations already carry the safety profile; the description covers the remaining gaps an agent needs — caching, rate limits, retry, folding semantics, and licensing. Nothing required to call 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 cross-parameter meaning: it clarifies that search_language changes what the query word itself means (lemma vs English gloss) and that ASCII input is folded to the reconstruction's diacritics with the resolution echoed back. It does not touch max_forms, leaving that entirely 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 Proto-Scythian lemma up on Wiktionary') and precisely enumerates the payload (senses plus full descendants, etymology, reflex tree down to Ossetian and Khotanese). The scope ('the full descendants payload' in one call) implicitly separates it from the sibling scythian_get_descendants, which only pieces out part of that payload.

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?

Gives clear mode-selection guidance: default 'xsc' looks a reconstructed lemma up directly, while search_language='eng' reverses the lookup via gloss matching and returns matching lemmas plus expanded entries. It does not, however, name a when-not condition or explicitly route the agent to the sibling tool for a narrower fetch.

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

All hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources