Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Edit a homebrew card

update_homebrew_box
DestructiveIdempotent

Replace a homebrew card's details. Returns: The card.

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>",
      "character": "<character>",
      "box": "<box>"
    },
    "name": "update_homebrew_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYesThe card's id.
costNoWhat using it takes.
diceNoA roll it makes that isn't an attack, like 1d8+2.
iconNoA glyph key from the app's icon set. Unknown keys fall back to the default.
nameNoWhat it is called. Required.
saveNoA saving throw it forces.
usesNoLimited uses, if it has any.
attackNoAn attack roll, if it makes one.
detailNoThe whole text, for the drawer.
summaryNoOne line for the card.
campaignYesThe campaign, by its slug (what its link says) or its id.
characterYesThe character, by its slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds only the word "Replace" (implying omitted fields may be dropped) and the return value "The card," which is genuinely useful since there is no output schema. It does not say what access level is required or what happens to fields left out of a 12-parameter replace.

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 short sentences, front-loaded with the action and followed by the return value; nothing is wasted. It is arguably under-sized for the complexity, but it is structurally clean rather than padded.

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?

The return value is covered inline, compensating for the missing output schema, but the description is very thin for a destructive 12-parameter replace with nested objects. An agent still lacks guidance on required permissions, partial-versus-full replacement, and when this is the right tool.

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 all 12 parameters, including the nested save/uses/attack objects, are already documented in the schema. The description adds no meaning beyond that, which meets the baseline 3 requirement but does not exceed it.

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?

"Replace a homebrew card's details" gives a specific verb and resource, and "Replace" conveys overwrite semantics rather than a partial patch. It never distinguishes itself from the sibling add_homebrew_box, so an agent must infer that create-versus-edit split on its own.

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?

The description contains no when-to-use guidance, no prerequisites, and no mention of alternatives such as add_homebrew_box for new cards or the read tools for fetching one. The agent gets no condition that tells it to pick this tool over its siblings.

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