Skip to main content
Glama
Sign In
mediawiki-mcp-server

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_get_stale_pages

Read-only

Find wiki pages not edited in a set number of days to identify stale content for review, with optional category or namespace filters.

Instructions

Find pages that haven't been edited in a specified number of days.

USE WHEN: User asks "find outdated pages", "which pages need review", "show stale content", "wiki hygiene check".

NOT FOR: Recent activity (use mediawiki_get_recent_changes). Not for orphaned pages (use mediawiki_find_orphaned_pages).

PARAMETERS:

  • days: Staleness threshold in days (default 90)

  • category: Limit to pages in this category (optional)

  • namespace: Namespace to check (default 0 = main)

  • limit: Max pages to return (default 50, max 200)

RETURNS: Stale pages sorted by last edit (oldest first), with days since edit and last editor.

Input Schema

NameRequiredDescriptionDefault
daysNoPages not edited in this many days (default 90)
limitNoMax pages to return (default 50, max 200)
categoryNoLimit to pages in this category
namespaceNoNamespace to check (default 0 = main)
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.

Output Schema

NameRequiredDescriptionDefault
messageYes
stale_countYes
stale_pagesYes
total_scannedYes
days_thresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.31.0
    • 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"
+}
  2. Addedv1.30.0

TDQS

A4.6/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, so safety profile is covered. The description adds useful context: default threshold of 90 days, sort order (oldest first), and returned fields (days since edit, last editor), which annotations don't convey. It doesn't mention rate limits or auth, but that's a minor gap given annotation coverage.

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 purpose sentence, then USE WHEN, NOT FOR, PARAMETERS, and RETURNS sections. Every line is scannable and earns its place; no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with an output schema covering return values, this is nearly complete: purpose, routing, params, and return summary are all present. It omits any mention of the rationale audit parameter and doesn't state pagination behavior, but those are minor given the output schema and annotations.

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 baseline is 3. The description goes slightly beyond by restating parameter meanings and defaults coherently in one block, but adds no syntax or format details not already in the schema. Note: rationale parameter is absent from the description entirely.

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 states a specific verb+resource+scope: find pages not edited in a specified number of days. It clearly distinguishes itself from siblings by naming both mediawiki_get_recent_changes and mediawiki_find_orphaned_pages as alternatives.

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?

Explicit USE WHEN triggers are given with quoted user phrasings, and NOT FOR exclusions name the exact alternative tools for adjacent use cases. This is textbook routing guidance.

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

Deploy Server

Other Tools