CwikiMCP

cwiki_list_pages

Retrieve a paginated list of pages from the Apache Incubator Confluence space, with an option to force refresh the cache.

Instructions

List pages in the configured Apache Incubator Confluence space.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cwiki_list_pages"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`start`	No
`force_refresh`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states only 'List pages' and omits pagination behavior (despite start/limit parameters), whether archived or restricted pages are included, cache refresh effects, or any side effects. This is insufficient for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence) but lacks necessary context. While conciseness is positive, the brevity results in incompleteness. It could be improved by adding a second sentence on usage or behavior.

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?

Given the presence of an output schema and three parameters with no descriptions, the description should at least mention the output format (list of page objects) and pagination semantics. It does not, and the tool's complete behavior (e.g., whether it returns all pages or respects limits) is unclear.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must explain the parameters. It mentions none of the three parameters (limit, start, force_refresh). The parameter titles are generic and their meanings (pagination control, cache bypass) are not communicated. This adds no value beyond the schema.

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 'list' and the resource 'pages in the configured Apache Incubator Confluence space', unambiguously differentiating from siblings like cwiki_search_pages (which searches) and cwiki_get_page (which retrieves a single page).

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?

The description implies usage for the single configured space but does not explicitly guide when to use this tool versus alternatives like cwiki_search_pages for filtered results or cwiki_get_children for hierarchical nav. No exclusions or conditions are mentioned.

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

Deploy Server