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

docmost-mcp-local

by wisflux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

get_page

Read-only

Fetch a Docmost page using its slug ID and return the content as Markdown.

Instructions

Fetch a Docmost page by slug ID and return its content as Markdown.

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": {
      "slug_id": "<slug_id>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
slug_idYesThe page slug ID returned from search_docs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds the behavioral trait that it returns Markdown content. No contradictions. Could mention error handling or rate limits but acceptable given 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?

Single sentence, no wasted words. Front-loads the action 'Fetch'. Perfectly concise.

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 simple one-parameter tool with no output schema, the description covers the main action and return format. Missing details on error behavior but acceptable for a read-only fetch.

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 coverage is 100% with one parameter fully described. The description's 'by slug ID' adds minimal extra meaning beyond the schema's description. Baseline 3 applies.

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 clearly states the verb 'Fetch', the resource 'Docmost page', the method 'by slug ID', and the output format 'as Markdown'. This distinguishes it from siblings like search_docs which returns a list of pages, not content.

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

Usage Guidelines3/5

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

Implied usage: the slug ID comes from search_docs, but no explicit guidance on when to use this tool versus alternatives like get_comments or list_child_pages. No when-not-to-use or exclusion 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