mediawiki-mcp-server

by olgasafonova

Overview Schema Source Related Servers Discussions Admin

Hybrid

mediawiki_get_page_summary

Read-only

Retrieve a wiki page's intro and key metadata to answer what a topic is about without downloading the entire page.

Instructions

Get lead section + key metadata without loading the full page.

USE WHEN: User asks "what is X about", "quick overview of X", "summarize the X page". Much lighter than mediawiki_get_page for large pages.

NOT FOR: Full page content (use mediawiki_get_page). Not for specific sections (use mediawiki_get_sections with section parameter).

PARAMETERS:

title: Page name (required)

RETURNS: Lead section (intro before first heading), page size, categories, section list, last edit timestamp.

Input Schema

Name	Required	Description	Default
`title`	Yes	Page title to get summary for
`rationale`	No	Optional one-sentence explanation of why you are calling this tool. Used for audit trails when present.

Output Schema

Name	Required	Description	Default
`title`	Yes
`format`	Yes
`length`	Yes
`message`	No
`page_id`	Yes
`redirect`	No
`sections`	No
`categories`	No
`last_edited`	Yes
`redirect_to`	No
`revision_id`	Yes
`lead_content`	Yes
`section_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.31.0May 14, 2026

addedInput schema / properties / rationale

Added value: +{
+  "description": "Optional one-sentence explanation of why you are calling this tool. Used for audit trails when present.",
+  "type": "string"
+}

Addedv1.30.0May 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds useful context beyond that: it is a lighter-weight read that avoids loading the full page, and it enumerates what comes back. The only omission is that idempotentHint=false isn't explained, but that is minor for a read tool.

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 one-line purpose followed by clearly labeled USE WHEN, NOT FOR, PARAMETERS, and RETURNS blocks. Every sentence earns its place and the routing constraint precedes the detail.

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?

For a simple two-parameter read tool with annotations and an output schema present, the description covers purpose, routing, inputs, and expected return content. An agent has everything needed to select and invoke it correctly; the RETURNS summary is a helpful convenience even if the output schema is authoritative.

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% and both parameters are documented there, so the schema carries the semantic load. The description restates the required 'title' parameter but adds no format, disambiguation, or title-resolution guidance beyond the schema, and it never mentions the optional 'rationale' parameter.

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+resource ('Get lead section + key metadata') and immediately scopes it ('without loading the full page'). It explicitly distinguishes itself from siblings mediawiki_get_page and mediawiki_get_sections, so an agent can disambiguate without opening a 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?

Dedicated USE WHEN and NOT FOR sections give explicit triggers ('what is X about', 'quick overview') and name the correct alternatives for the excluded cases (full content → get_page, specific sections → get_sections with section param). Nothing is left to inference.

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

Deploy Server