Skip to main content
Glama

mediawiki_get_page_summary

Read-onlyIdempotent

Retrieve the lead section and key metadata of a wiki page, including categories, page size, section list, and last edit timestamp, to provide a quick overview without loading the full content.

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

TableJSON Schema
NameRequiredDescriptionDefault
titleYesPage title to get summary for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
page_idYes
lead_contentYes
formatYes
lengthYes
revision_idYes
last_editedYes
categoriesNo
section_countYes
sectionsNo
redirectNo
redirect_toNo
messageNo
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true. The description adds value by detailing what is returned (lead section, page size, categories, etc.) and the lightweight nature. 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 structured with clear sections (USE WHEN, NOT FOR, PARAMETERS, RETURNS) and no wasted words. Every sentence adds value, making it easy for the agent to parse quickly.

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 the tool's simplicity (1 parameter, read-only, with output schema), the description covers all necessary context: what it returns, when to use, and alternatives. It is fully complete for decision-making.

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 coverage is 100% with a single parameter 'title' described as 'Page title to get summary for.' The description restates it as 'Page name (required),' adding no significant meaning beyond the schema. Baseline 3 is appropriate.

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 'Get lead section + key metadata without loading the full page,' providing a specific verb and resource. It distinguishes itself from siblings like mediawiki_get_page (full page) and mediawiki_get_sections (specific sections).

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?

Explicitly specifies when to use ('USE WHEN: User asks...') and when not to use ('NOT FOR: Full page content...'), naming alternative siblings. This provides clear guidance for the agent.

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/olgasafonova/mediawiki-mcp-server'

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