Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Mark a page as somebody's character

link_wiki_page_to_seat
Idempotent

Tie a wiki page to the seat whose character it is, so every mention wears their face. Null unties it. A player links their own; the GM may link anybody's. 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>",
      "memberId": "<memberId>"
    },
    "name": "link_wiki_page_to_seat"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe wiki page, by its slug (or its id).
campaignYesThe campaign, by its slug (what its link says) or its id.
memberIdYesThe seat's id, or null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true and destructive=false; the description adds what the annotations cannot: that this is an authorization-gated write (self vs GM), that null performs a reversible unlink, and that the call returns the page. It leaves out what happens on a seat from another campaign or a missing page.

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?

Three short sentences, front-loaded with the action, then permission model, then return value in a labeled form. The casual phrasing ("wears their face") is compact rather than wasteful, though slightly informal for a mutation description.

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 three-parameter, fully documented mutation with no output schema, the definition covers action, authorization, unlink semantics and the return value. Remaining gaps are edge cases (invalid seat, cross-campaign seat, failed link response) rather than missing core guidance.

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 page/campaign/memberId are already documented including the nullable seat id. The description only adds the semantic consequence of null ("unties it") and frames memberId as a "seat"; useful but marginal against a fully documented schema, so the baseline 3 applies.

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 ("Tie a wiki page to the seat whose character it is") plus the concrete effect ("every mention wears their face") and the inverse operation ("Null unties it"). An agent can distinguish this from assign_character or create_wiki_page without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit permission-based routing: "A player links their own; the GM may link anybody's", and explains the unlink path via null. It does not explicitly name a sibling alternative (e.g. assign_character) or state prerequisites like the page already existing, so it stops short of full when/when-not guidance.

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