mcp-mediawiki-crunchtools

List Pages Tool

list_pages_tool

Read-only

List wiki pages by namespace and optional title prefix, with limits and pagination support for browsing MediaWiki content.

Instructions

List wiki pages with optional prefix filter.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pages_tool"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.1Oct 22, 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"
```
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

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered structurally, but the description adds nothing beyond that - no mention of result ordering, pagination behavior via from_title, or the default/max limit. With an annotation present the bar is lower, yet the description contributes essentially zero behavioral context of its own.

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?

A single compact sentence with zero filler, and the core action is front-loaded. Nothing is redundant or padded relative to what it says.

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

Completeness3/5

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

An output schema exists and all parameters are schema-documented, so the basics are covered. But for a listing tool with a pagination parameter and overlapping siblings, the description omits the distinction from search_tool and any pagination/ordering note, leaving a small but real gap given the sibling landscape.

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%, so all four parameters (limit, prefix, namespace, from_title) are already documented with defaults and semantics. The description only restates the prefix filter and adds no syntax, interaction, or edge-case detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb (list) and resource (wiki pages) plus a qualifier (optional prefix filter), so the agent instantly knows the operation. However, it does not differentiate from siblings like search_tool, get_page_tool, or list_recent_changes_tool, which overlap in retrieving page collections.

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

Usage Guidelines3/5

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

Usage is only implied: 'List wiki pages' suggests enumeration, and 'optional prefix filter' hints at prefix-scoped listing. There is no explicit when-to-use guidance (e.g., use instead of search_tool when you need a full or prefix-scoped enumeration), and no mention of when not to use it.

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