Skip to main content
Glama
Sign In
leafwiki-mcp

leafwiki-mcp

by ipapadop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

compare_page_revisions

Compare two historical page revisions to see what changed between a base and target snapshot. Use page ID or path to identify the content and review differences.

Instructions

Compare two historical page snapshots.

Args: base_revision_id: Revision used as the comparison base. target_revision_id: Revision compared with the base. id: Page identifier, preferred when both selectors are supplied. path: Slash-separated page path.

Returns: Revision comparison returned by LeafWiki.

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": {
      "base_revision_id": "<base_revision_id>",
      "target_revision_id": "<target_revision_id>"
    },
    "name": "compare_page_revisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
pathNo
base_revision_idYes
target_revision_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether the operation is read-only, whether auth/permissions are needed, or what the diff contains; 'Revision comparison returned by LeafWiki' merely restates the purpose rather than disclosing behavior.

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?

Front-loaded purpose sentence followed by clearly labeled Args and Returns sections; no wasted prose. The Returns line has little informational value, which keeps it just short of a 5.

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 not be explained, and the parameters are covered. What is missing is positioning against the many revision/page siblings and any statement of the operation's safety profile, which no annotation supplies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is the only source of parameter meaning, and it documents all four: base vs target revision roles, and the id-vs-path selector with an explicit precedence rule ('id preferred when both selectors are supplied'). This meaningfully exceeds the bare schema.

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 clear verb+resource: comparing two historical page snapshots. An agent can distinguish it from get_page_revision or list_page_revisions by the comparative nature, though the description never explicitly names those siblings.

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?

No when-to-use guidance, no prerequisites, and no alternatives named despite several revision-related siblings (get_page_revision, list_page_revisions). The only routing hint is 'id preferred when both selectors are supplied', which concerns parameters rather than tool selection.

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