github-wiki-mcp

by andreahaku

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

append_to_wiki_page

Append markdown content to a GitHub wiki page. Creates the page automatically when missing.

Instructions

Append content to an existing wiki page. If the page does not exist, creates it with the provided content.

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": {
      "owner": "<owner>",
      "repo": "<repo>",
      "token": "<token>",
      "pageName": "<pageName>",
      "content": "<content>"
    },
    "name": "append_to_wiki_page"
  }
}

Input Schema

Name	Required	Description
`repo`	Yes	GitHub repository name
`owner`	Yes	GitHub repository owner (username or organization)
`token`	Yes	GitHub personal access token with repo scope
`content`	Yes	Markdown content to append
`pageName`	Yes	Name of the wiki page to append to
`commitMessage`	No	Optional commit message (defaults to "Append to {pageName}")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals a non-obvious trait: the tool creates the page if it does not exist, which is more than the name alone suggests. However, it does not mention error conditions, permission checks (beyond token schema), or response structure, slightly limiting transparency.

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 extremely concise, using two short sentences that front-load the primary action and then add the fallback behavior. Every word earns its place, with no extraneous content.

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 append operation, the description covers the core behavior and the schema covers all parameters. No output schema is needed. The only gaps are minor edge cases (e.g., empty content, encoding) and explicit comparison with siblings, but overall it is sufficiently complete given the tool's simplicity.

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 description coverage is 100%, so the baseline is 3. The description reinforces that 'content' is appended and 'pageName' is the target, but it does not add parameter-specific details beyond the schema. This is acceptable since the schema already documents each parameter well.

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 a specific action ('Append content to an existing wiki page') with a defined resource ('wiki page'). The fallback behavior ('If the page does not exist, creates it') further distinguishes it from the sibling 'write_wiki_page', which implies overwriting rather than appending.

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 behavior implies usage – you use it when you want to add content without replacing existing content – but it does not explicitly compare against alternatives like 'write_wiki_page' or specify when to prefer one over the other. There are no exclusions or prerequisites beyond what the schema already notes.

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

Deploy Server