mcp-mediawiki-crunchtools

Search Tool

search_tool

Read-only

Perform full-text searches across a MediaWiki instance to find pages, with options to set the result limit and namespace.

Instructions

Full-text search across the wiki.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_tool"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return (default: 10, max: 50)
`query`	Yes	Search query string
`namespace`	No	Namespace to search in (0=Main, default: 0)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.2.1Oct 22, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results to return (default: 10, max: 50)"
```
- addedInput schema / properties / namespace / description
```
Added value: +"Namespace to search in (0=Main, default: 0)"
```
- addedInput schema / properties / query / description
```
Added value: +"Search query string"
```
Changed3 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / limit / description
```
Removed value: -"Maximum results to return (default: 10, max: 50)"
```
- removedInput schema / properties / namespace / description
```
Removed value: -"Namespace to search in (0=Main, default: 0)"
```
- removedInput schema / properties / query / description
```
Removed value: -"Search query string"
```
Changed3 schema fields changedMay 4, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results to return (default: 10, max: 50)"
```
- addedInput schema / properties / namespace / description
```
Added value: +"Namespace to search in (0=Main, default: 0)"
```
- addedInput schema / properties / query / description
```
Added value: +"Search query string"
```
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?

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds nothing beyond that — no ranking behavior, result shape, or pagination/limit interaction context. With an output schema present the return format needn't be spelled out, but 'full-text' semantics (matching, scoring) are left entirely opaque.

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?

One front-loaded sentence with zero waste. It is efficient but borders on under-specified rather than maximal conciseness; a short clause on scope would still earn its place.

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?

For a 3-parameter read-only tool with a full output schema, the safety and parameter burden is carried by structured fields. What remains missing is the routing decision among many sibling listing/search tools, which is the one thing the description should have supplied.

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 coverage is 100% with clear descriptions for limit, query, and namespace, so baseline is 3. The description adds no extra meaning — e.g., what namespace scope means for search reach or how limit interacts with ranking — beyond what the schema already says.

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 ('Full-text search') and resource ('across the wiki'), which is enough to distinguish a search operation from get_page_tool or list_pages_tool. It stops short of explicitly contrasting with those siblings, so it lands at 4.

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 search versus browsing with list_pages_tool or list_recent_changes_tool, and no mention of when results are or aren't appropriate. The single sentence implies lookup usage but excludes nothing.

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