Skip to main content
Glama

Approve wiki page

approve_wiki_page

Approve a wiki page IN YOUR OWN NAME, in the edition you read: 'version' is the page's version as get_wiki_page gave it, and the call is refused if the page has been edited since — read it again first. The approval is a line in the page's journal: who, when, which edition, and an optional note. It is never edited or deleted (withdraw_wiki_page_approval adds a line that takes it back). A later edit of the page does not remove it — the page then says that the edition in force is the approved one and the newer text is not approved. Only the project's lead (or the company's owner or an admin), or somebody named on the page with ask_wiki_page_approval. Approving is a person's statement: do it when your person told you to, not because a page looks finished. On a page read as signatures (get_wiki_page_approval's 'mode') this is the person's SIGNATURE of that edition — never sign in anybody's name but theirs, and never on your own initiative.

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": {
      "id": "<id>",
      "version": "<version>"
    },
    "name": "approve_wiki_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPage id.
noteNoAn optional note kept with the approval, e.g. the decision it rests on.
versionYesThe version you read and are approving.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, closed-world mutation; the description adds substantial context — an immutable journal line recording who/when/which edition, that later edits do not erase it, that a stale version is refused, and the permission model. It does not describe the response payload, but that is minor.

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

Conciseness4/5

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

Front-loads the core action and version precondition, then layers authorization and signature semantics, which are genuinely needed. It is dense and parenthetical in places but nearly every sentence carries information an agent must act on.

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

Completeness5/5

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

For a 3-parameter mutation with no output schema, the definition covers permissions, staleness handling, reversibility, signature mode, and the effect of later edits. Nothing an agent needs in order to call it correctly appears to be missing.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description still adds meaning by tying 'version' to the value returned by get_wiki_page and explaining the optimistic-concurrency refusal, which the schema's 'the version you read and are approving' only hints at.

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?

States a specific verb and resource (approve a wiki page) plus the scope qualifier 'in your own name, in the edition you read'. It is clearly distinguishable from withdraw_wiki_page_approval and get_wiki_page_approval, which are named in the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance ('do it when your person told you to, not because a page looks finished'), names the alternative that reverses it (withdraw_wiki_page_approval), and specifies a precondition — re-read the page if it has been edited since. It also names who is permitted to call it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources