Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

List the table's sheet designs

list_sheet_frames
Read-onlyIdempotent

Sheet shapes designed with Blank Slate and kept at this table for the next player. Returns: The frames.

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_sheet_frames"
  }
}

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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds only 'kept at this table for the next player', which hints at scoping but explains nothing about ordering, filtering by campaign, or what a 'frame' contains.

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?

It is short at two sentences, but the first is jargon-dense and the second ('Returns: The frames.') restates the name without adding information. Nothing is front-loaded as an explicit action statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list with a fully described single parameter and annotations covering safety, this is close to adequate. However, with no output schema, the description should say more about what a returned 'frame' is, and the 'Blank Slate' terminology is left undefined.

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% and the single campaign parameter is fully documented in the schema as slug or id. The description adds no syntax, default, or interpretation beyond that, so the baseline of 3 applies.

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 says it lists 'sheet shapes designed with Blank Slate' kept at the table, which conveys a list-of-designs resource, but relies on unexplained product jargon ('Blank Slate', 'frames') and never states the plain verb+resource. It does not distinguish this from the sibling save_sheet_frame, so an agent can't tell the read from the write without reading names.

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 statement of when to use this versus save_sheet_frame or update_custom_sheet; the phrase 'for the next player' hints at intent but is not actionable guidance. No prerequisites or exclusions are given.

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