hub

Get an Interslavic inflection table

interslavic_get_inflections

Read-onlyIdempotent

Fetch the full declension (noun/adjective) or conjugation (verb) table for a word 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": } — switch on result.category ('noun' | 'adjective' | 'verb' | 'not_found') before reading the body. Tables are generated by the official Interslavic morphology engine, not attested.

Input Schema

Name	Required	Description	Default
`entry_id`	Yes	The dictionary word id from a search result's inflection handle (a number, e.g. '33555') — NOT the headword itself (Interslavic homographs share a spelling).
`word_class`	Yes	The paradigm class from a search result's inflection handle: 'noun', 'adjective' or 'verb'.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 13, 2026
- addedInput schema / properties / word_class / enum
```
Added value: +[
+  "adjective",
+  "noun",
+  "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 ]+$"
```
AddedJul 12, 2026

TDQS

A4.7/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, openWorld=false, non-destructive), and the description adds genuine context beyond them: the provenance caveat that tables come from the official morphology engine and are 'not attested', plus guidance to switch on result.category before reading the body. Return-shape detail partially overlaps the existing output schema, so this stops 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the action and immediately followed by the exclusion condition. No filler, and the return-shape/category caveat is placed after the routing guidance where it is needed.

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 rich annotations, a full output schema, and 100% parameter description coverage, the description supplies everything an agent needs to decide to call it and how to interpret the response. Nothing material 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 both parameters are already documented individually; the baseline would be 3. The description adds a small but real layer by framing entry_id + word_class jointly as the 'inflection handle' from a search result, telling the agent the two values are consumed as a pair rather than independently.

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?

The description names a specific verb and resource ('Fetch the full declension (noun/adjective) or conjugation (verb) table') and scopes it to a word identified by a search result's inflection handle. It is clearly distinguishable from the sibling interslavic_search, which produces those handles.

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?

Explicit when-not guidance is given: '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.' The agent is told both the trigger and the reason the tool is usually unnecessary, which is exactly the routing information needed.

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?