Skip to main content
Glama
Sign In

hub

by com.valksor
OverviewDiscussionsAdmin

Get an Old Norse inflection table

norse_get_inflections
Read-onlyIdempotent

Fetch the full declension (nominals) or conjugation (verbs — active AND mediopassive) tables 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. 'maðr', 'kasta'.
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ÁáÉéÍíÓóÚúÝýÆæÐðÞþǪǫØøŒœǾǿÖö][A-Za-zÁáÉéÍíÓóÚúÝýÆæÐðÞþǪǫØøŒœǾǿÖö\\-']{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 / NorseNominalParadigm / properties / source / default
      Previous value: -"Wiktionary, the free dictionary (en.wiktionary.org), Old Norse 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), Old Norse 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 / NorseVerbalParadigm / properties / source / default
      Previous value: -"Wiktionary, the free dictionary (en.wiktionary.org), Old Norse 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), Old Norse 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), Old Norse 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), Old Norse 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: +"norse_get_inflectionsArguments"
    • changedOutput schema / title
      Previous value: -"get_inflectionsOutput"New value: +"norse_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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld). Beyond that, the description discloses the return surface (Markdown plus structuredContent) and the not_found outcome the agent must branch on, which is genuinely useful behavioral context not in the annotations.

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 action, then the gating condition, then the return shape — a sensible order. It is dense with parenthetical asides and the license line is arguably marginal, but no sentence is 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?

Given an outputSchema exists, the description need not explain return values, yet it briefly flags the category switch agent should branch on. Combined with the usage gate and parameter provenance, an agent has everything needed to invoke it correctly.

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 description coverage is 100%, so the baseline is 3, but the description adds provenance semantics the schema lacks: entry_id + word_class come as a pair from a search result's inflection handle and must be used together. It doesn't document enum values or the pattern beyond what the schema already gives.

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?

Names a specific verb (fetch) and resource (full declension/conjugation tables) and specifies the exact key (a search result's inflection handle) needed to identify the target. It is clearly a follow-up to the norse_search sibling, so an agent can tell which tool owns the lookup vs. which owns the table.

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?

States an explicit when-to-use and when-NOT-to-use rule: call this only when a search ran without inline forms or left a match un-expanded, because a default search already returns the table inline. That routing condition is exactly what an agent needs to avoid redundant calls.

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