Skip to main content
Glama
Sign In
CwikiMCP

CwikiMCP

by justinmclean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cwiki_get_children

Retrieve a list of child pages for a specified Confluence wiki page by providing its page ID. Optionally set limit, start offset, and force refresh.

Instructions

List child pages for a page by 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": "cwiki_get_children"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
limitNo
startNo
force_refreshNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 fully disclose behavior. It only states 'List child pages' without specifying that it is a read-only operation, describing pagination behavior (limit/start), or clarifying side effects like caching force_refresh. This lack of transparency leaves important behavioral traits undocumented.

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 concise at one sentence, but conciseness must balance with informativeness. It omits crucial details about parameters and usage, so it is under-specified rather than efficiently packed.

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 absence of annotations, output schema content is not shown but exists, yet the description does not mention return values. Sibling tools are listed but not differentiated. This incompleteness forces the agent to guess at nuances.

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%, yet the description adds no meaning to any of the four parameters (page_id, limit, start, force_refresh). With no parameter explanations, the agent cannot correctly construct queries or interpret defaults, making the tool difficult to use correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'List' and the resource 'child pages' with the key parameter 'by page id'. It is specific and well-defined, but does not explicitly distinguish from sibling tools like cwiki_get_page or cwiki_list_pages, which could cause ambiguity for an AI agent.

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 is provided on when to use this tool versus alternatives such as cwiki_search_pages or cwiki_list_pages. There is no mention of prerequisites or context, leaving the agent without directional cues for selection.

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