Skip to main content
Glama

scythian

by com.valksor
OverviewDiscussionsAdmin

Get a Proto-Scythian entry's descendants

scythian_get_descendants
Read-onlyIdempotent

Fetch the full descendants payload — etymology, glosses and the reflex tree (Sarmatian→Alanic→Ossetian, Saka→Khotanese) — for a lemma identified by a search result's descendant handle (entry_id + word_class). Use this only when a search ran without inline payloads or left a match un-expanded — a default search already returns each match's payload inline. Returns Markdown plus the payload as structuredContent with the shape {"result": } per the declared outputSchema — switch on result.category ('descendants' | 'not_found') before reading the body. Content from en.wiktionary.org (CC BY-SA 4.0).

Input Schema

NameRequiredDescriptionDefault
entry_idYesThe bare lemma (no asterisk) from a search result's descendant handle, e.g. 'tiɣri', 'baga' — a typed leading asterisk is tolerated.
word_classYesThe part-of-speech section from a search result's descendant handle, e.g. 'noun', 'adjective', 'proper noun'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / entry_id / pattern
      Added value: +"^\\*?[^\\W\\d_][\\w\\u0300-\\u036F'-]{0,79}$"
    • addedInput schema / properties / word_class / enum
      Added value: +[
+  "abbreviation",
+  "acronym",
+  "adjective",
+  "adverb",
+  "affix",
+  "article",
+  "character",
+  "circumfix",
+  "classifier",
+  "combining form",
+  "conjunction",
+  "contraction",
+  "counter",
+  "determiner",
+  "diacritical mark",
+  "idiom",
+  "infix",
+  "initialism",
+  "interfix",
+  "interjection",
+  "letter",
+  "ligature",
+  "noun",
+  "number",
+  "numeral",
+  "participle",
+  "particle",
+  "phrase",
+  "postposition",
+  "prefix",
+  "preposition",
+  "prepositional phrase",
+  "pronoun",
+  "proper noun",
+  "proverb",
+  "punctuation mark",
+  "romanization",
+  "root",
+  "suffix",
+  "symbol",
+  "verb"
+]
    • removedInput schema / properties / word_class / maxLength
      Removed value: -24
    • removedInput schema / properties / word_class / minLength
      Removed value: -1
    • removedInput schema / properties / word_class / pattern
      Removed value: -"^[a-z ]+$"
    • changedOutput schema / $defs / DescendantsNotFound / properties / source / default
      Previous value: -"Wiktionary, 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)"New value: +"Wiktionary, 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: https://creativecommons.org/licenses/by-sa/4.0/) Adapted: reformatted and condensed from the original."
    • changedOutput schema / $defs / ScythianDescendants / properties / source / default
      Previous value: -"Wiktionary, 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)"New value: +"Wiktionary, 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: https://creativecommons.org/licenses/by-sa/4.0/) Adapted: reformatted and condensed from the original."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds substantial context: return format (Markdown + structuredContent), response shape, the result.category switch ('descendants'|'not_found'), and licensing. Missing explicit auth/rate-limit notes, keeping it just below top.

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 purpose, then usage constraint, then return shape. Every sentence earns its place. Slightly dense but no filler; could be marginally tighter.

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 2-param read tool with an output schema, annotations, and 100% schema coverage, the description covers provenance, use conditions, return shape, and the category discriminator. Nothing an agent needs 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 baseline is 3, but the description adds genuine meaning: it clarifies that entry_id + word_class come from a 'search result's descendant handle', which ties the parameters to their provenance beyond the schema's field-level docs.

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+resource ('Fetch the full descendants payload') and enumerates what it contains (etymology, glosses, reflex tree). Clearly distinguishes itself from the sibling scythian_search by naming search results as the input handle source.

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?

Explicitly states when to use it ('only when a search ran without inline payloads or left a match un-expanded') and when not to ('a default search already returns each match's payload inline'). This is exactly the routing guidance an agent needs.

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

All scythian 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