Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Change my seat

update_my_seat

Your name, colour and picture at this table, and whether you are emailed when the GM posts a session's notes. The GM's colour is gold and stays gold. Returns: The seat.

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": "update_my_seat"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoYour name at this table.
colorNoYour colour, as one of the offered hex values.
campaignYesThe campaign, by its slug (what its link says) or its id.
avatarUrlNoA picture's web address. Null inherits your character's.
notesEmailNoEmail me when the GM posts a session's notes here. On by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / notesEmail
      Added value: +{
+  "description": "Email me when the GM posts a session's notes here. On by default.",
+  "type": "boolean"
+}
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent write, so the description need not restate that. It adds a genuine behavioral constraint ('The GM's colour is gold and stays gold') and a return hint ('Returns: The seat'), but omits key write semantics such as whether omitted fields are left untouched and what permissions are required.

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

Conciseness3/5

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

Three short sentences with no padding, but the lead sentence is a noun-phrase fragment rather than a front-loaded statement of what the tool does, which weakens orientation. The GM-colour exception is well placed as a follow-up.

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 five-parameter mutation with full schema coverage and no output schema, the description plus the 'Returns: The seat' note covers most of what an agent needs. The remaining gap is partial-update behavior and the significance of the required campaign parameter.

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 enum colour values, the slug-or-id campaign, and the null-inherits-character avatar rule are already documented. The description paraphrases the same fields and adds nothing beyond the schema, and it never mentions the required 'campaign' parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the mutable attributes (name, colour, picture, notes email) but never uses an action verb, so the 'update' intent must be inferred from the title 'Change my seat'. It is distinguishable from get_my_seat only indirectly, via the wording 'stays gold' which implies a write.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no reference to the obvious alternatives (get_my_seat for reading, update_participant for editing someone else's seat). The only conditional information is the implicit rule that the GM's colour cannot be changed.

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