Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Rename or reorder a map

update_map

Rename a map the GM added, or move it one place along the tabs (move: -1 or 1). GM only. Returns: The map.

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>",
      "map": "<map>"
    },
    "name": "update_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapYesThe map's id.
moveNo-1 to move it left, 1 to move it right.
nameNoA new name.
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.7/5.0
Behavior4/5

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

Annotations already declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, and the description still adds the GM-only authorization requirement plus the return value ('Returns: The map.'). It omits edge behavior such as invalid move at a boundary or a no-op call, which keeps it from a 5.

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?

Two compact sentences with the primary operation front-loaded and the authorization note placed immediately after. Slightly telegraphic phrasing ('one place along the tabs') costs a bit of clarity but nothing is wasted.

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?

No output schema exists, yet the description states what is returned, and combined with full schema coverage and annotations an agent has enough to call it correctly. The main residual gap is the rename-vs-move exclusivity rule, which is not spelled out.

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 schema already documents all four parameters including the -1/1 semantics for move and the slug-or-id form of campaign. The description only repeats the move values and adds no format or constraint detail beyond the schema, which is the baseline case.

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?

States a specific verb+resource pair ('rename a map', 'move it one place along the tabs') that an agent can distinguish from the read-only sibling list_maps without opening the schema. It stops short of naming the sibling alternative explicitly, but the operation is 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?

Adds a real prerequisite ('GM only') that tells the agent who may call it, and the 'move: -1 or 1' note implies the two modes (rename vs reorder). However, it never states that exactly one of name/move should be supplied per call, nor what happens if both or neither are provided, leaving mode selection 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