Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Share or hide the memorial

set_memorial_public

Make the memorial page public (anybody with the link, and search engines) or the table's alone again. GM only. Returns: The memorial state.

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>",
      "public": "<public>"
    },
    "name": "set_memorial_public"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicYesPublic or not.
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?

Beyond the annotations, the description explains the real-world consequence of going public — anyone with the link and search-engine indexing — which gives meaning to openWorldHint. It also adds the GM-only authorization requirement, a key behavioral fact the annotations do not express. It stops short of saying whether a re-call is harmless or what flipping back hides.

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, front-loaded with the action and its effect, with no filler. The middle clause is slightly awkward in phrasing but costs little.

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?

A two-parameter toggle with full schema coverage and annotations: the description covers the action, the visibility semantics, the permission gate, and the return value. Nothing an agent needs in order to call it correctly 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%, so both parameters are already documented, establishing a baseline of 3. The description does add meaning to the boolean by clarifying that 'public' includes link-sharing and search-engine visibility, but it adds nothing about the campaign slug/id parameter.

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?

Names a specific verb and resource ('make the memorial page public') and defines both ends of the toggle, so an agent can distinguish it from the read-only sibling get_memorial. The phrase 'or the table's alone again' is slightly loose but still conveys the private direction of the switch.

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?

Supplies a clear precondition ('GM only') which tells the agent who may call it. It does not explicitly address when to use this versus inspecting state first via get_memorial, so the usage guidance is implied rather than spelled out.

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