wiktionary-de-mcp

Get raw wikitext

get_raw_wikitext

Read-onlyIdempotent

Retrieve raw German Wiktionary wikitext when structured lookups miss translations, references, or other page details; use section and offset to page through long pages.

Instructions

Return the unprocessed wikitext source of a de.wiktionary.org page.

Use only when lookup_word omits something you need (e.g. translations,
references). Pages can be very long (100k+ characters), so prefer `section`
and page through with `offset` when the result says it was truncated.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Exact page title (case-sensitive), e.g. 'Haus' or 'Flexion:gehen'.
`offset`	No	Character offset to start from, for paging through long pages.
`section`	No	Only return the part of the page under the first heading or section marker containing this text, e.g. 'Übersetzungen', 'Referenzen', 'Englisch'. Omit for the whole page.
`max_chars`	No	Maximum characters to return.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 18, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful operational behavior: pages can exceed 100k characters, results may indicate truncation, and paging via `section` and `offset` is recommended. It does not add auth or rate-limit details, but the annotations lower the burden.

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?

Three tightly written sentences. The core purpose is front-loaded, the usage restriction follows immediately, and the paging advice is placed last where it belongs. 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?

The description covers when to use the tool, its relationship to lookup_word, and how to handle long/truncated results. With full schema descriptions, annotations, and an output schema present, no additional detail is required for an agent to call 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 would be 3 even without description help. The description still adds strategic meaning by explaining when and how to use `section` and `offset` for long pages. It does not elaborate on `title` or `max_chars`, but the schema already documents those fully.

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 uses a specific verb and resource: 'Return the unprocessed wikitext source of a de.wiktionary.org page.' It clearly distinguishes itself from lookup_word by specifying raw source output. An agent can identify this as the low-level wikitext access tool without opening the schema.

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?

It explicitly says to use this only when lookup_word omits needed content such as translations or references, naming the sibling alternative and the condition for switching. It also gives practical guidance to prefer `section` and page with `offset` when truncation occurs.

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

Deploy Server