mcp-mediawiki-crunchtools

Parse Wikitext Tool

parse_wikitext_tool

Read-only

Convert raw wikitext to HTML, optionally supplying a page title for template resolution.

Instructions

Parse raw wikitext to HTML.

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": {
      "wikitext": "<wikitext>"
    },
    "name": "parse_wikitext_tool"
  }
}

Input Schema

Name	Required	Description	Default
`title`	No	Context page title for template resolution (optional)
`wikitext`	Yes	Raw wikitext content to parse

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.1Oct 22, 2026
- addedInput schema / properties / title / description
```
Added value: +"Context page title for template resolution (optional)"
```
- addedInput schema / properties / wikitext / description
```
Added value: +"Raw wikitext content to parse"
```
Changed2 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / title / description
```
Removed value: -"Context page title for template resolution (optional)"
```
- removedInput schema / properties / wikitext / description
```
Removed value: -"Raw wikitext content to parse"
```
Changed2 schema fields changedMay 4, 2026
- addedInput schema / properties / title / description
```
Added value: +"Context page title for template resolution (optional)"
```
- addedInput schema / properties / wikitext / description
```
Added value: +"Raw wikitext content to parse"
```
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=true annotation already establishes that this is a non-mutating operation, so the description's only obligation is to add context — template resolution behavior, how the optional title affects output, or what happens with malformed wikitext. It adds none of that; the entire description just restates the operation. The one useful detail (title for template resolution) lives only in the schema.

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 terse sentence with no waste, and the operation/transformation is front-loaded. It is arguably too terse rather than bloated, which is penalized in contextual completeness rather than here.

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, so return values need no explanation, and the input schema fully documents both parameters. However, a wikitext parser has real behavioral subtleties (template/module expansion, dependence on title, error handling on invalid markup) that go unmentioned, leaving the definition only minimally adequate.

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%, with both parameters documented inline, including the optional title's role in template resolution. The description contributes nothing beyond the schema, so the baseline 3 applies.

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 (parse) and the exact transformation (raw wikitext to HTML), which is unambiguous about what comes in and what comes out. It does not distinguish itself from the sibling get_page_html_tool, which also yields HTML, so an agent can't be fully certain from the description alone which one to reach for.

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 when-to-use guidance, no prerequisites, and no mention of the sibling alternatives such as get_page_html_tool or get_page_tool. The agent must infer the use case purely from the verb.

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