Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

List battles

list_battles
Read-onlyIdempotent

Every battle at the table, newest first: drafts, the one under way, and the ended. GM only. Returns: Battle summaries.

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

Input Schema

NameRequiredDescriptionDefault
campaignYesThe campaign, by its slug (what its link says) or its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description still adds real value beyond them: the newest-first ordering, the fact that drafts and ended battles are included (unusual for a listing), and the GM-only access requirement, which no annotation conveys.

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?

Three short clauses front-load the scope and ordering, then the access constraint, then the return type. No filler, nothing repeated from the schema, and the most decision-relevant information comes first.

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 read-only, one-parameter listing with no output schema, the description covers scope, ordering, access control, and return shape. It could say slightly more about what a 'battle summary' contains or whether results are capped, but nothing essential to correct invocation is 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 single parameter is fully documented in the schema, including the slug-or-id flexibility. The description adds nothing about the campaign parameter, so the baseline of 3 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 names the resource (battles), the ordering (newest first), and the full scope (drafts, the one under way, and the ended), so an agent knows this is a complete, unfiltered listing rather than a single lookup like get_battle. It stops short of explicitly naming the sibling alternatives, but the verb+resource+scope combination is specific and unambiguous.

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?

'GM only' is a useful gate, and enumerating the three battle states implies no filtering is needed. However, there is no explicit guidance on when to choose get_battle instead of this tool, or what happens for a non-GM caller, leaving the alternative-selection reasoning to 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