mcp-mediawiki-crunchtools

list_pages_tool

List wiki pages by namespace and optional title prefix, with pagination and result limits, returning page titles and metadata for MediaWiki browsing.

Instructions

List wiki pages with optional prefix filter.

Args: prefix: Filter pages starting with this prefix namespace: Namespace to list (0=Main, default: 0) limit: Maximum results (default: 50, max: 500) from_title: Start listing from this title (for pagination)

Returns: List of page titles with metadata

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`prefix`	No
`namespace`	No
`from_title`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / from_title / description
```
Removed value: -"Start listing from this title (for pagination)"
```
- removedInput schema / properties / limit / description
```
Removed value: -"Maximum results (default: 50, max: 500)"
```
- removedInput schema / properties / namespace / description
```
Removed value: -"Namespace to list (0=Main, default: 0)"
```
- removedInput schema / properties / prefix / description
```
Removed value: -"Filter pages starting with this prefix"
```
Changed4 schema fields changedMay 4, 2026
- addedInput schema / properties / from_title / description
```
Added value: +"Start listing from this title (for pagination)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results (default: 50, max: 500)"
```
- addedInput schema / properties / namespace / description
```
Added value: +"Namespace to list (0=Main, default: 0)"
```
- addedInput schema / properties / prefix / description
```
Added value: +"Filter pages starting with this prefix"
```
First observedv0.1.3Mar 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations provided, but description compensates by documenting pagination behavior ('from_title' for pagination) and return structure ('List of page titles with metadata'). Includes constraint documentation (limit max: 500) which provides behavioral boundaries.

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?

Uses structured docstring format (Args/Returns) with zero redundancy. Each sentence earns its place: first line states purpose, Args clarify semantics, Returns clarify output. Appropriate length for parameter complexity.

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?

Given 4 parameters with 0% schema coverage, the description successfully documents all inputs. Output schema exists (per context signals), so minimal return value description ('List of page titles with metadata') is sufficient. Missing only sorting order or rate limit details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the Args section comprehensively documents all 4 parameters: prefix semantics ('starting with'), namespace encoding ('0=Main'), limit constraints ('default: 50, max: 500'), and pagination purpose ('Start listing from this title'). Fully compensates for schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'List' and resource 'wiki pages' with scope 'optional prefix filter'. Distinguishes from singular 'get_page_tool' but does not explicitly differentiate from 'search_tool' or 'get_category_members_tool' which also return page lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this versus 'search_tool' (full-text search) or 'get_category_members_tool' (category-based listing). No mention of prerequisites or workflow integration despite pagination support being documented.

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