Skip to main content
Glama

paradigm

Read-onlyIdempotent

Generate complete inflection paradigms for Estonian words: up to 28 noun forms (14 cases × 2 numbers) or 30 verb forms (infinitives, tenses, participles).

Instructions

Generate the full inflection paradigm for an Estonian word.

For nominals (nouns, adjectives, pronouns, numerals): produces all 14 cases × 2 numbers = up to 28 forms. For verbs: produces infinitives, present/past/conditional indicative, imperative, and participles (~30 forms). Other parts of speech (adverbs, conjunctions, particles) don't inflect — forms is empty.

Each form entry has the Vabamorf form code (e.g. sg p, ksin), its Estonian label (e.g. ainsuse osastav, tingiv 1.p ainsus), and the surface form Vabamorf generated. Use form_estonian verbatim in Estonian replies — don't translate the English form code.

Phase-1 scope: covers the most commonly-needed forms per word class, not every theoretical form Vabamorf can produce. Single-word input, capped at 200 characters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wordYesA single Estonian word (lemma or inflected form) to generate the full paradigm for.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
formsNo
inputNo
lemmaNo
word_classNo
partofspeechNo
summary_estonianNo
Behavior5/5

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds valuable context: character limit (200), single-word input, handling of parts of speech that don't inflect, and instructions to use 'form_estonian' verbatim. No contradictions.

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?

The description is concise and well-structured: front-loaded with the main purpose, followed by details on nominal vs verb forms, phase-1 scope, and output usage. Every sentence serves a purpose.

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 that an output schema exists (not shown but confirmed by context signals), the description adequately covers input constraints (single word, Estonian, 200 char), scope (phase-1), and output format (Vabamorf codes, Estonian labels, surface forms). Complete for a paradigm generation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter 'word' with a clear schema description. The description adds the nuance that it can be a lemma or inflected form and imposes a 200-character cap, which enriches the schema meaning.

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 clearly states the tool generates the full inflection paradigm for an Estonian word, specifying for nominals (14 cases × 2 numbers) and verbs (~30 forms), and distinguishes from siblings by noting it covers phase-1 scope and is for single-word input.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use (for an Estonian word needing full paradigm) and what forms are included, but does not explicitly contrast with sibling tools like 'analyze_morphology' or provide 'when not to use' guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/silly-geese/estonian-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server