Skip to main content
Glama
Sign In

hub

by com.valksor
OverviewDiscussionsAdmin

Get a Latin inflection table

latin_get_inflections
Read-onlyIdempotent

Fetch the full declension (nominals) or conjugation (verbs) table for a lemma identified by a search result's inflection handle (entry_id + word_class). Use this only when a search ran without inline forms or left a match un-expanded — a default search already returns each match's table inline. Returns Markdown plus the table as structuredContent with the shape {"result": } per the declared outputSchema — switch on result.category ('nominal' | 'verbal' | 'not_found') before reading the body. Content from en.wiktionary.org (CC BY-SA 4.0).

Input Schema

NameRequiredDescriptionDefault
entry_idYesThe Wiktionary page title (the lemma) from a search result's inflection handle, e.g. 'amo', 'aqua'.
word_classYesThe part-of-speech section from a search result's inflection handle, e.g. 'verb', 'noun', 'adjective'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / entry_id / pattern
      Added value: +"^[A-Za-zĀāĒēĪīŌōŪūȲȳÄäÖöËë\\-']{1,80}$"
    • 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 / LatinNominalParadigm / properties / source / default
      Previous value: -"Wiktionary, the free dictionary (en.wiktionary.org), Latin 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), Latin 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 / LatinVerbalParadigm / properties / source / default
      Previous value: -"Wiktionary, the free dictionary (en.wiktionary.org), Latin 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), Latin 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 / ParadigmNotFound / properties / source / default
      Previous value: -"Wiktionary, the free dictionary (en.wiktionary.org), Latin 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), Latin 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. Changed2 schema fields changed
    • changedInput schema / title
      Previous value: -"get_inflectionsArguments"New value: +"latin_get_inflectionsArguments"
    • changedOutput schema / title
      Previous value: -"get_inflectionsOutput"New value: +"latin_get_inflectionsOutput"
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds real behavioral context beyond that: the not_found case and the need to switch on result.category before reading the body, plus the Wiktionary source/license. It omits any rate-limit or caching behavior, keeping it short of a 5.

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 the when-to-use caveat; every clause carries information. The final attribution line is required but the middle sentences are dense and could be tightened slightly.

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 restate return values, yet it still gives the consumption pattern (switch on result.category) and the not_found branch. Combined with annotations covering the safety profile, nothing needed 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 baseline is 3. The description adds provenance semantics beyond the schema by defining the pair as a 'search result's inflection handle (entry_id + word_class)', telling the agent where the values come from rather than just their types.

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 (fetch the full declension/conjugation table) and clarifies the nominal-vs-verbal split, so the agent knows exactly what it returns. It is clearly distinguishable from latin_search and latin_lemmatize among its siblings.

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 says when NOT to use it: 'Use this only when a search ran without inline forms or left a match un-expanded — a default search already returns each match's table inline.' This routes the agent away from redundant calls without inference.

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