Skip to main content
Glama
Sign In
docmost-community-mcp

docmost-community-mcp

by dilruwanm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_history_version

Read-only

Retrieve a specific page history version using its history ID to access past content for review or restoration.

Instructions

Get a specific page history version by history ID.

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": {
      "history_id": "<history_id>"
    },
    "name": "get_history_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
history_idYesHistory version UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 and destructiveHint=false, so the read-only nature is fully covered. The description adds no further behavioral details, such as behavior for an invalid history ID or what fields the returned version contains, but nothing contradicts the annotations.

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?

One short, front-loaded sentence contains all essential information with no filler. Every word contributes to the meaning, making it highly scannable for an agent.

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?

For a single-parameter read-only fetch with strong annotations, the description is adequate and clear. The only notable gap is the absence of any return-value description, which matters more because there is no output schema to fill that gap.

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?

The sole parameter history_id is fully documented in the schema as 'History version UUID', and the description repeats the 'by history ID' concept without adding format or usage details. With 100% schema coverage, the baseline of 3 is appropriate.

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?

Clearly states the operation ('Get'), the resource ('specific page history version'), and the lookup key ('by history ID'). This distinguishes it from the sibling get_page_history, which retrieves a page's history list rather than a single version.

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 guidance on when to use this tool versus alternatives such as get_page_history (for listing versions) or restore_page (for restoring a version). The description merely states the action without any context, exclusions, or selection criteria.

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