Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Add a seat

add_seat

Offer somebody a seat by name and address. Nobody is emailed: the answer carries the seat's own join link. Campaign owner only. Returns: The seat and its join link.

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>",
      "name": "<name>",
      "email": "<email>"
    },
    "name": "add_seat"
  }
}

Input Schema

NameRequiredDescriptionDefault
isDmNoWhether this seat is the GM's.
nameYesTheir name at the table.
emailYesTheir address.
campaignYesThe campaign, by its slug (what its link says) or its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the mutation and safety annotations, it discloses that nobody is emailed, states the owner-only restriction, and says the response contains both the seat and its join link. These details cover the important behavioral surprises an agent would otherwise have to infer.

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 action is front-loaded, followed by side-effect, permission, and result information in four very short sentences. There is slight overlap between the two join-link mentions, but the wording remains exceptionally economical and easy to scan.

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 flat four-parameter mutation with complete schema descriptions, the description supplies the remaining operational context and, absent an output schema, explicitly states the return value. An agent has enough information to invoke it correctly, with only broader sibling-selection guidance missing.

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%, and the schema already explains the campaign slug or id, table name, email address, and GM meaning of isDm. The description's 'name and address' wording mostly repeats that information and adds no further formats or constraints, so the schema-driven baseline applies.

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 states a specific action and resource: offering somebody a seat by name and address, with campaign-owner context. It does not explicitly distinguish this operation from the closely related add_participant or other seat and invitation tools.

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?

The no-email behavior and returned join link establish a manual-invitation workflow, while 'Campaign owner only' provides an explicit authorization prerequisite. There is no direct when-not guidance or routing to add_participant or respond_to_invitation, so selection among siblings still requires inference.

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