hub

Look a Church Slavonic word up

slavonic_search

Read-onlyIdempotent

Look an Old Church Slavonic word up on Wiktionary and return its senses plus full declension/conjugation tables — attested content (singular, dual and plural), 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 an English word instead: the result lists its per-sense Old Church Slavonic 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

Name	Required	Description	Default
`query`	Yes	The word to look up, in the language search_language names. Church Slavonic (default): a SINGLE Old Church Slavonic word in Cyrillic, any form — an inflected form ('бога') is resolved to its lemma ('богъ') automatically via cached paradigms, and the result says so; normalized OCS spelling works best, but titlos/accents and modern-Cyrillic respellings (ы for ꙑ) are folded. English (search_language='eng'): the English word whose Old Church Slavonic equivalents you want — multiword entries like 'apple tree' work.
`max_forms`	No	Optional 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_forms`	No	When true (default), each match's full declension/conjugation table is returned INLINE — usable cases/tenses (singular, dual AND plural) in ONE call, no follow-up slavonic_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 OCS entries; the per-sense translations list itself is always returned.
`search_language`	No	Language the query word is in: 'chu' (default) looks the Old Church Slavonic word up directly; 'eng' finds the OCS equivalents of an English word (per-sense, from Wiktionary's translation tables) and returns their full entries. Glosses are in English either way.	chu

Output Schema

TableJSON Schema

Name	Required	Description	Default
`found`	Yes	False when nothing matched. For an eng query, True means Old Church Slavonic translations were found — entries may still be empty when none of them could be expanded (see translations).
`query`	Yes
`source`	No		Wiktionary, the free dictionary (en.wiktionary.org), Old Church Slavonic entries. Wikimedia Foundation. Text available under CC BY-SA 4.0; attribution and share-alike required when republishing. (CC BY-SA 4.0)
`entries`	No
`handles`	No
`language`	Yes
`translations`	No	Populated only for eng queries (always [] for chu): the OCS terms each English sense translates to, in sense order. Entries/handles below are the expanded dictionary entries of those terms.
`resolved_from`	No	The original inflected query when resolved; else empty. chu queries only — always empty for eng results.
`search_method`	No	How 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_lemma`	No	The lemma actually searched when resolved; else empty. chu queries only — always empty for eng results.
`forms_truncated`	No	How many handles did NOT get an inline table because the per-search cap was reached.
`translations_truncated`	No	How 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.

AddedJul 21, 2026
RemovedJul 21, 2026

Changed6 schema fields changedJul 6, 2026

changedInput schema / properties / include_forms / description

Previous value: -"When true (default), each match's full declension/conjugation table is returned INLINE — usable cases/tenses (singular, dual AND plural) in ONE call, no follow-up 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 OCS entries; the per-sense translations list itself is always returned."New value: +"When true (default), each match's full declension/conjugation table is returned INLINE — usable cases/tenses (singular, dual AND plural) in ONE call, no follow-up slavonic_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 OCS entries; the per-sense translations list itself is always returned."

changedInput schema / title

Previous value: -"search_slavonicArguments"New value: +"slavonic_searchArguments"

changedOutput schema / $defs / Entry / properties / entry_id / description

Previous value: -"Page title — feed to get_inflections."New value: +"Page title — feed to slavonic_get_inflections."

changedOutput schema / $defs / Entry / properties / word_class / description

Previous value: -"POS section — feed to get_inflections."New value: +"POS section — feed to slavonic_get_inflections."

changedOutput schema / $defs / InflectionHandle / description

Previous value: -"A structured anchor for fetching a full paradigm: feed ``entry_id`` (the page\ntitle) + ``word_class`` (the POS section) to ``get_inflections`` — or ask\n``search`` to include the table inline (``forms``)."New value: +"A structured anchor for fetching a full paradigm: feed ``entry_id`` (the page\ntitle) + ``word_class`` (the POS section) to ``slavonic_get_inflections`` — or ask\n``search`` to include the table inline (``forms``)."

changedOutput schema / $defs / TranslationTerm / description

Previous value: -"One Old Church Slavonic word a translations table offers for an English\nsense. ``word`` is the Wiktionary page title in Cyrillic (what an ``eng``\nsearch re-searches and what ``get_inflections`` needs); only the Cyrillic\nscript row is read — the parallel Glagolitic spelling is the same lemma on a\nsoft-redirect page, so surfacing it would only duplicate the term."New value: +"One Old Church Slavonic word a translations table offers for an English\nsense. ``word`` is the Wiktionary page title in Cyrillic (what an ``eng``\nsearch re-searches and what ``slavonic_get_inflections`` needs); only the Cyrillic\nscript row is read — the parallel Glagolitic spelling is the same lemma on a\nsoft-redirect page, so surfacing it would only duplicate the term."

First observedJun 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/destructive, and the description adds substantial beyond-schema behavior: server-side caching, polite upstream pacing, rate-limit errors that should be retried after a wait, the Markdown + structuredContent return shape, and CC BY-SA attribution obligations. 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?

Core purpose and the two modes are front-loaded in the first sentence, and the caching/rate-limit/licensing caveats are correctly deferred to a second paragraph. The first paragraph is dense and slightly repetitive about inflection resolution, keeping it from a 5.

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?

An output schema exists and the description correctly avoids re-explaining return fields, only noting Markdown plus structuredContent. Combined with the mode semantics, caching behavior and retry guidance, an agent has everything needed to call this correctly.

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 description coverage is 100%, so the schema already documents query, max_forms, include_forms and search_language thoroughly. The description restates the same mode semantics and inflection-resolution behavior rather than adding new parameter meaning, so baseline 3 applies.

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) and resource (Old Church Slavonic word on Wiktionary) plus the exact return payload (senses, declension/conjugation tables). It also distinguishes the two operating modes and names slavonic_get_inflections as the follow-up it makes unnecessary, so an agent can tell it apart from 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?

Gives explicit context for 'chu' vs 'eng' queries and states that include_forms=true means no follow-up call to slavonic_get_inflections is needed, which routes the agent well. It does not mention when to prefer the transliterate/detransliterate siblings, so it stops short of full when/when-not coverage.

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

All hub tools Inspect

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

Need Help?