mcp-mediawiki-crunchtools

List Recent Changes Tool

list_recent_changes_tool

Read-only

List recent wiki edits with filters for namespace, tag, change type, and timestamp to monitor activity and identify updates.

Instructions

List recent edits 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_recent_changes_tool"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Filter by tag name
`limit`	No	Maximum results (default: 50, max: 500)
`namespace`	No	Filter by namespace (default: all namespaces)
`change_type`	No	Filter by type: edit, new, log, categorize, external
`from_timestamp`	No	Start from this timestamp (ISO 8601)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.2.1Oct 22, 2026
- addedInput schema / properties / change_type / description
```
Added value: +"Filter by type: edit, new, log, categorize, external"
```
- addedInput schema / properties / from_timestamp / description
```
Added value: +"Start from this timestamp (ISO 8601)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results (default: 50, max: 500)"
```
- addedInput schema / properties / namespace / description
```
Added value: +"Filter by namespace (default: all namespaces)"
```
- addedInput schema / properties / tag / description
```
Added value: +"Filter by tag name"
```
Changed5 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / change_type / description
```
Removed value: -"Filter by type: edit, new, log, categorize, external"
```
- removedInput schema / properties / from_timestamp / description
```
Removed value: -"Start from this timestamp (ISO 8601)"
```
- removedInput schema / properties / limit / description
```
Removed value: -"Maximum results (default: 50, max: 500)"
```
- removedInput schema / properties / namespace / description
```
Removed value: -"Filter by namespace (default: all namespaces)"
```
- removedInput schema / properties / tag / description
```
Removed value: -"Filter by tag name"
```
Changed5 schema fields changedMay 4, 2026
- addedInput schema / properties / change_type / description
```
Added value: +"Filter by type: edit, new, log, categorize, external"
```
- addedInput schema / properties / from_timestamp / description
```
Added value: +"Start from this timestamp (ISO 8601)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results (default: 50, max: 500)"
```
- addedInput schema / properties / namespace / description
```
Added value: +"Filter by namespace (default: all namespaces)"
```
- addedInput schema / properties / tag / description
```
Added value: +"Filter by tag name"
```
First observedv0.1.3Mar 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The readOnlyHint annotation already establishes this as a safe read operation. The description adds only 'recent edits' without defining recency, ordering, pagination behavior, or any rate/limit context, so it contributes very little beyond the annotation.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficiently sized, though its brevity reflects under-specification rather than deliberate minimization.

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?

With annotations, a full output schema, and complete parameter descriptions, the structured fields carry most of the burden. Still, the description does not clarify recency scope or sibling-tool selection, leaving gaps for an agent deciding between this and related list/search tools.

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%, and all five optional parameters are documented in the schema. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline 3 is 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?

The description gives a specific verb ('List') and resource ('recent edits on the wiki'), so the tool's basic purpose is clear. It does not, however, distinguish this from siblings like list_user_contributions_tool or search_tool, leaving the agent to infer the difference.

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 versus searching, listing a user's contributions, or fetching page history. No alternatives or exclusions are named, so the agent must guess at the appropriate context.

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