Retrieve a Nextcloud Collective page as markdown, including its metadata and body, by specifying the collective ID and page ID.
Fetch a page as markdown. Returns the metadata block followed by the page body.
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | Yes | ||
| collectiveId | Yes |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and non-destructive behavior. The description adds clarity about the return format (metadata block and markdown body), which is useful context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence that communicates the essential information without unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description explains the output format well, which is important given the absence of an output schema. It does not cover error cases, but for a simple read operation this is acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The parameter names 'collectiveId' and 'pageId' are somewhat self-explanatory, but the description provides no additional explanation and the schema has no parameter descriptions, leaving the relationship between the two IDs implicit.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (fetch), the resource (a page), and the output format (markdown with metadata block and body), distinguishing it from other page-related tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The verb 'fetch' implies usage when retrieving a page's content, but there is no explicit guidance on when to use this tool versus alternatives like list_pages or get_backlinks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.