Skip to main content
Glama
Sign In

hub

by com.valksor
OverviewDiscussionsAdmin

Get an Old English inflection table

anglo_get_inflections
Read-onlyIdempotent

Fetch the full declension (nominals, including the pronouns' dual) 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. 'cyning', 'bindan'.
word_classYesThe part-of-speech section from a search result's inflection handle, e.g. 'verb', 'noun', 'adjective', 'pronoun'.

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 / AngloNominalParadigm / properties / source / default
      Previous value: -"Wiktionary, the free dictionary (en.wiktionary.org), Old English 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 English 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 / AngloVerbalParadigm / properties / source / default
      Previous value: -"Wiktionary, the free dictionary (en.wiktionary.org), Old English 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 English 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 English 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 English 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.4/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/idempotent/destructive, so the safety profile is handled. The description adds real operational context: two return forms (Markdown + structuredContent), and instruction to switch on result.category ('nominal' | 'verbal' | 'not_found') before reading the body, which is non-obvious behavioral guidance beyond 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 purpose, then the when-to-use constraint, then return shape, then license. Slightly dense (Gutenberg-era contested duals parenthetical), but every sentence carries information an agent needs. No waste.

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?

Despite having an output schema, the description still adds the category-switch guidance and the dual return medium, which are the non-obvious bits. Combined with full param coverage and clear use-condition, an agent has everything needed to call this correctly and to route to it versus anglo_search.

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% — both entry_id and word_class are documented in the schema with examples and (for word_class) a full enum. The description restates 'entry_id + word_class' without adding format/syntax meaning beyond the schema, so baseline 3 is appropriate.

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 (fetch) and resource (declension/conjugation table for a lemma identified via inflection handle), and enumerates what the table covers (nominals incl. pronouns' dual, verbs). Distinguishes itself from anglo_search by requiring an inflection handle rather than a query.

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 '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 is a clear when-to-use/when-not-to-use discriminator against the sibling anglo_search.

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