docmost-mcp-local

by wisflux

Overview Schema Source Related Servers Discussions Admin

Rust

Local

get_comments

Read-only

Retrieve comments from a Docmost page using its ID. Optionally limit results or paginate with a cursor.

Instructions

List Docmost comments for a page 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": {
      "page_id": "<page_id>"
    },
    "name": "get_comments"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional number of comments to return.
`cursor`	No	Optional cursor returned by a previous list call.
`page_id`	Yes	The Docmost page ID to list comments for.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true, so the agent knows this is a read operation. The description adds that it lists comments for a page ID, which is consistent. However, it does not disclose pagination behavior even though the schema includes cursor and limit parameters, nor does it mention potential errors or rate limits. This is adequate but not enriched.

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 description is a single sentence, concise and front-loaded with the core action. However, it lacks any additional structure such as examples or notes, but it does not contain any fluff. It earns a 4 because it is efficient but minimally informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema, the description should clarify what is returned, but it does not. It also fails to explain pagination despite the presence of cursor and limit parameters. Given the complexity of 3 parameters and no output schema, the description is incomplete for an agent to fully understand the tool's behavior.

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 schema already provides descriptions for all three parameters (100% coverage), so the description does not add new semantic meaning beyond restating the resource. According to the rules, with high schema coverage the baseline is 3, and the description does not exceed that.

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?

The description uses a specific verb 'List' with a clear resource 'Docmost comments' and scope 'for a page ID', which distinguishes it from sibling tools like create_comment or update_comment that perform different actions. The purpose is immediately obvious.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it does not mention that this tool should be used to retrieve comments, while create_comment is for adding new ones. This omission forces the agent to infer usage from the tool name alone.

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