Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_parse

Read-only

Parse wikitext into rendered HTML to preview wiki markup and test syntax before saving.

Instructions

Parse wikitext and return rendered HTML.

USE WHEN: User wants to preview wikitext rendering, test markup syntax.

PARAMETERS:

  • wikitext: Wikitext content to parse (required)

  • title: Context page title for link resolution (optional)

RETURNS: Rendered HTML output.

Input Schema

NameRequiredDescriptionDefault
titleNoPage title for context (affects template expansion)
wikitextYesWikitext content to parse
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.

Output Schema

NameRequiredDescriptionDefault
htmlYes
linksNo
messageNo
truncatedNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.31.0
    • addedInput schema / properties / rationale
      Added value: +{
+  "description": "Optional one-sentence explanation of why you are calling this tool. Used for audit trails when present.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds that output is rendered HTML, but since an output schema exists this is largely redundant, and it does not explain the non-idempotent behavior (template/parser-dependent output) that the annotation flags.

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?

The USE WHEN / PARAMETERS / RETURNS sections are front-loaded and easy to scan, with one line each. The RETURNS line duplicates an existing output schema, which is the only real waste.

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?

Given one required param, 100% schema coverage, and an output schema in place, the description covers purpose, usage, parameters, and return type adequately. It is complete for a parsing tool, with only the non-idempotent behavior left undescribed.

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%, so the baseline is 3. The description restates both parameters but adds only a marginal gloss ('title: context page title for link resolution') that is slightly inconsistent with the schema wording ('affects template expansion').

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+resource+output: 'Parse wikitext and return rendered HTML.' This clearly separates it from conversion siblings like mediawiki_convert_markdown or mediawiki_apply_formatting, which transform rather than render. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'USE WHEN: preview wikitext rendering, test markup syntax' line gives concrete, actionable context for selecting this tool. However, it offers no when-not guidance and no named alternative for related tasks (e.g. rendering vs converting), so it stays at 4.

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

Deploy Server

Other Tools