cc-agent

get_wiki_page

Retrieve a specific wiki page from a repository by providing the repository URL and page name. Enables documentation access for autonomous agent workflows.

Instructions

Return a single wiki page by name for a repo.

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": {
      "repo_url": "<repo_url>",
      "page": "<page>"
    },
    "name": "get_wiki_page"
  }
}

Input Schema

Name	Required	Description	Default
`page`	Yes	Page name to retrieve
`repo_url`	Yes	Repository URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.16.15Jul 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries full burden for behavioral disclosure. It states basic behavior but does not specify return format, error handling, or whether page name is case-sensitive. Minimal but not misleading.

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?

The description is a single concise sentence that immediately states the action and resource. No redundant words, perfectly front-loaded.

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

Completeness3/5

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

No output schema exists, and the description does not specify what is returned (page content? metadata?). Given sibling tools and lack of output structure, the description is somewhat incomplete for agent to handle the response.

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%, so parameters are already documented. The description adds no extra meaning beyond 'by name for a repo'—no details on format, constraints, or examples. Baseline 3, no extra value.

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 specific verb 'Return' and resource 'a single wiki page by name for a repo'. It distinguishes this tool from siblings like list_wiki_pages (multiple pages) and get_wiki (possibly entire wiki).

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 does not provide guidance on when to use this tool vs alternatives (e.g., list_wiki_pages for all pages, get_wiki for full wiki). Usage is implied but no explicit context or exclusions.

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