Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Rename a battle or set the turn

update_battle

Change the battle's name, its round, or whose turn it is. GM only. Returns: The battle.

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>",
      "battle": "<battle>"
    },
    "name": "update_battle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA new name.
roundNoThe round.
battleYesThe battle's id.
campaignYesThe campaign, by its slug (what its link says) or its id.
turnIndexNoWhose turn, as a place in the order from 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already state that this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The description adds the authorization requirement ('GM only') and the return value ('Returns: The battle'). It does not say whether omitted fields are left unchanged or what happens when round and turnIndex disagree.

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, with the action and affected fields front-loaded, then the permission gate, then the return value. Every sentence earns its place, though 'Returns: The battle' is slightly terse.

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 tool, the description covers purpose, permission and return value, and the schema fully documents every parameter. It leaves a gap around the interaction between round and turnIndex and around whether the call is a partial patch.

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 each of the five parameters is already documented in the schema and the baseline is 3. The description maps its three clauses to the name, round, and turnIndex parameters but adds nothing about formats or the relationship between round and turnIndex.

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 verb and resource ('Change the battle's...') and enumerates the mutable fields: name, round, turn. However, it overlaps with the sibling next_turn, which also advances whose turn it is, and the description does not explain the distinction.

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?

The 'GM only' line gives a clear permission prerequisite, which is real usage guidance. There is no when-to-use or when-not-to-use guidance relative to siblings such as next_turn, create_battle, end_battle, or update_participant, so the agent must infer which tool performs turn changes.

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