Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Edit a wiki page

update_wiki_page

Change a page's name, type, text or pictures. Fields left out stay as they are; the slug never moves on a rename. Every version is kept. Returns: The page.

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": {
      "campaign": "<campaign>",
      "page": "<page>"
    },
    "name": "update_wiki_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoThe whole text, as it should now read.
nameNoThe new name.
pageYesThe wiki page, by its slug (or its id).
typeNoWhat it is.
campaignYesThe campaign, by its slug (what its link says) or its id.
coverUrlNoThe page's cover. Null takes it off.
avatarUrlNoThe page's face. Null takes it off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds real value on top: partial-update semantics, the guarantee that the slug is unchanged by a rename, and that every version is retained (implying changes are recoverable). It omits permission/auth requirements and any rate-limit behavior.

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?

Four short clauses, front-loaded with the action, then the update semantics, the slug guarantee, version retention, and the return value. Nothing is padded or redundant.

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 7-parameter mutation tool with no output schema, the definition covers the essentials: what can change, that omissions are preserved, identifier stability, version history, and what comes back. Authorization expectations and error behavior are the only meaningful gaps.

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

Parameters4/5

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

Schema description coverage is 100%, which sets a baseline of 3, but the description adds meaning beyond it: it maps the plain-language categories (name, type, text, pictures) onto the name/type/body/coverUrl/avatarUrl fields and clarifies that renaming does not alter the page identifier used by the `page` parameter. That mapping is a small but genuine addition over the schema's per-field text.

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 opens with a specific verb and resource ("Change a page's name, type, text or pictures") and enumerates the mutable fields, so an agent knows exactly what this does. It is clearly the edit counterpart to create_wiki_page and get_wiki_page, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the tool for modifying an existing page while create_wiki_page makes new ones. The partial-update rule ("Fields left out stay as they are") is genuinely useful selection context. No exclusions or explicit alternatives are named.

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

All Tavern toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources