mcp-mediawiki-crunchtools

List Files Tool

list_files_tool

Read-only

Lists files on a wiki with filters for prefix, MIME type, and pagination by filename.

Instructions

List files on the wiki.

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_files_tool"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results (default: 50, max: 500)
`prefix`	No	Filter files starting with this prefix
`from_name`	No	Start listing from this file (for pagination)
`mime_type`	No	Filter by MIME type (e.g., "image/png")

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_name / description
```
Added value: +"Start listing from this file (for pagination)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results (default: 50, max: 500)"
```
- addedInput schema / properties / mime_type / description
```
Added value: +"Filter by MIME type (e.g., \"image/png\")"
```
- addedInput schema / properties / prefix / description
```
Added value: +"Filter files starting with this prefix"
```
Changed4 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / from_name / description
```
Removed value: -"Start listing from this file (for pagination)"
```
- removedInput schema / properties / limit / description
```
Removed value: -"Maximum results (default: 50, max: 500)"
```
- removedInput schema / properties / mime_type / description
```
Removed value: -"Filter by MIME type (e.g., \"image/png\")"
```
- removedInput schema / properties / prefix / description
```
Removed value: -"Filter files starting with this prefix"
```
Changed4 schema fields changedMay 4, 2026
- addedInput schema / properties / from_name / description
```
Added value: +"Start listing from this file (for pagination)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results (default: 50, max: 500)"
```
- addedInput schema / properties / mime_type / description
```
Added value: +"Filter by MIME type (e.g., \"image/png\")"
```
- addedInput schema / properties / prefix / description
```
Added value: +"Filter files starting with this prefix"
```
First observedv0.1.3Mar 30, 2026

TDQS

C2.6/5.0

Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description should add context such as ordering, pagination behavior, or what a file entry contains. It adds nothing beyond the annotations and the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and waste-free, but it is under-specified rather than appropriately sized for a tool with pagination and filtering options. Brevity here reflects missing content, not efficiency.

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 the schema documents all parameters, so the essentials are covered. However, with four params including a pagination cursor, the description should at least signal ordering and how from_name relates to limit; that context is absent.

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?

All four parameters have full schema descriptions (limit, prefix, from_name pagination, mime_type), so the schema carries parameter semantics completely. The description contributes no additional meaning, which is the baseline 3 case at 100% coverage.

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

Purpose3/5

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

The description states a specific verb and resource ("List files") on the wiki, which is clear enough in isolation. But it does not distinguish this from sibling list tools such as list_pages_tool, list_categories_tool, or get_file_info_tool, leaving the agent to infer the boundary between listing files and listing other resources.

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?

There is no guidance on when to use this tool rather than get_file_info_tool or list_pages_tool, and no mention of preconditions or exclusions. The only usage hints (prefix, mime_type filtering, pagination) live in the schema, not the description.

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