Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Import a character from a character-sheet link

add_character_from_beyond

Import a public character sheet from an online character builder into this table, by its link or its number. One way: nothing is written back to the sheet's site. Returns: The character's slug.

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>",
      "source": "<source>"
    },
    "name": "add_character_from_beyond"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesThe sheet's link or number id.
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, open-world, and non-idempotent profile, but the description adds genuinely new behavior: "nothing is written back to the sheet's site," which bounds the blast radius of an external fetch. It also supplies a return value (the character's slug) in the absence of an output schema.

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, front-loaded sentences with no filler; the action and inputs come first, then the side-effect guarantee, then the return value. The phrasing "One way:" is slightly awkward but still earns its place by preventing an agent from assuming a bidirectional sync.

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 two-parameter import tool with no output schema, the description covers the action, both inputs, the external-side safety guarantee, and the return value. Minor gaps remain around duplicate imports and failure modes for private sheets, but nothing essential to calling it 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 in the schema, and the description's "by its link or its number" largely restates the source parameter's own text. "Into this table" loosely maps to the campaign parameter without adding format or resolution detail, so baseline 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 gives a specific verb and resource: "Import a public character sheet from an online character builder into this table," which an agent can distinguish from sibling creation paths like create_custom_character or start_character_draft. It stops short of naming those siblings, so the differentiation is inferential rather than explicit.

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?

Usage context is implied by "public character sheet ... by its link or its number," which carries the prerequisite that the sheet must be publicly reachable. There is no explicit statement of when to choose this over create_custom_character, start_character_draft, or sync_character, and no guidance about what to do after import.

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