mcp-mediawiki-crunchtools

search_tool

Find wiki pages using full-text queries, filter by namespace, and limit results to retrieve matching titles, snippets, and metadata.

Instructions

Full-text search across the wiki.

Args: query: Search query string namespace: Namespace to search in (0=Main, default: 0) limit: Maximum results to return (default: 10, max: 50)

Returns: Search results with titles, snippets, and metadata

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`namespace`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.1/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It usefully describes return contents (titles, snippets, metadata) but omits safety declarations (read-only status), rate limits, or search index freshness that would help an agent understand operational constraints.

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?

Front-loaded purpose statement followed by structured Args and Returns sections. Zero waste — every line provides essential information about parameters or output shape that is missing from the schema.

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?

Complete documentation for a 3-parameter search tool with simple types. Acknowledges output schema existence by summarizing return structure. Slight gap on behavioral edge cases, but adequate given the tool's straightforward read-only nature.

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 fully compensates by documenting all three parameters: query semantics, namespace mapping (0=Main), and limit constraints (default: 10, max: 50). Excellent compensation for schema deficiencies.

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

Purpose5/5

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

States 'Full-text search across the wiki' — specific verb (search), clear resource (wiki), and 'full-text' distinguishes it from sibling get_page_tool (direct retrieval) and list_pages_tool (enumeration).

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?

The term 'Full-text search' implies keyword-based lookup versus exact page retrieval, but there is no explicit guidance on when to choose this over get_page_tool or list_pages_tool, nor any mention of prerequisites.

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