estonian-mcp

check_capitalization

Read-onlyIdempotent

Flag incorrectly capitalized Estonian weekdays, months, nationalities, and country names before language nouns in mid-sentence text; skips sentence starts and acronyms.

Instructions

Flags words wrongly capitalized mid-sentence (algustäheortograafia):

weekday, month, nationality: lowercase except at sentence start (esmaspäeval, jaanuaris, eestlane).
language-adjective: a country name before a language or culture noun is lowercase (eesti keel, vene kultuur). On its own it is the country (Eesti, Eestis) and is not flagged.

Sentence-initial words and all-caps acronyms are skipped. A hit that opens a line, list item or quotation, or sits in a proper name (Eesti Keele Instituut), is usually false. English title case in headings is check_translationese's title-case.

Input Schema

Name	Required	Description	Default
`text`	Yes	Estonian text.

Output Schema

Name	Required	Description	Default
`issues`	No
`summary_estonian`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.9.0Oct 24, 2026
- changedInput schema / properties / text / description
```
Previous value: -"Estonian text to check for capitalization errors (Algustäheortograafia)."New value: +"Estonian text."
```
- removedInput schema / properties / text / title
```
Removed value: -"Text"
```
- removedInput schema / title
```
Removed value: -"check_capitalizationArguments"
```
- removedOutput schema / properties / issues / default
```
Removed value: -null
```
- removedOutput schema / properties / issues / items / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / issues / title
```
Removed value: -"Issues"
```
- removedOutput schema / properties / note
```
Removed value: -{
-  "default": null,
-  "title": "Note",
-  "type": "string"
-}
```
- removedOutput schema / properties / summary_estonian / default
```
Removed value: -null
```
- removedOutput schema / properties / summary_estonian / title
```
Removed value: -"Summary Estonian"
```
- removedOutput schema / properties / text
```
Removed value: -{
-  "default": null,
-  "title": "Text",
-  "type": "string"
-}
```
- removedOutput schema / title
```
Removed value: -"_CheckResult"
```
First observedv0.2.4Jul 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover safety (readOnlyHint=true, idempotentHint=true, openWorldHint=false), so the bar is lower, yet the description adds real behavioral detail the annotations can't: which categories are suppressed (sentence-initial, all-caps acronyms) and which hits are likely false positives (line/list/quotation openers, proper names like Eesti Keele Instituut). That false-positive guidance is exactly what prevents an agent from over-reporting.

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?

Front-loaded with the core action, then bulleted category rules with parenthetical examples, then a compact caveat block. Every sentence carries information (category definition, exception, or false-positive warning); no filler or restatement of the name.

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?

An output schema exists, so return-value explanation is unnecessary; the description instead supplies the decision logic an agent needs — what counts as a hit, what is skipped, and when a hit should be ignored. Combined with the readOnly/idempotent annotations, nothing material is missing for correct invocation and interpretation.

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?

One parameter with 100% schema description coverage ('Estonian text.'), so the schema carries the parameter burden and baseline 3 applies. The description adds only implicit confirmation that input is Estonian prose subject to capitalization rules; it says nothing about handling markdown, HTML, mixed-language spans, or multi-paragraph input.

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 ('Flags words wrongly capitalized mid-sentence') plus the Estonian orthography term, and immediately enumerates the exact categories it covers (weekday, month, nationality, language-adjective). It also explicitly excludes the sibling's territory ('English title case in headings is check_translationese's `title-case`'), so an agent can distinguish it from the 28 siblings without opening schemas.

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?

Gives clear inclusion rules with examples (esmaspäeval, jaanuaris, eestlane) and explicit exclusions: sentence-initial words and all-caps acronyms are skipped, and line/list/quotation openers or proper names are 'usually false'. It routes one adjacent case to check_translationese. It doesn't state input-language prerequisites beyond the schema's 'Estonian text', but the when-to-use boundary is essentially complete.

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