Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Send a message

send_message

Write in a conversation. Anybody in a direct conversation may; only the GM posts in the Game Master thread (table). [[Name]] links a wiki page. Everybody else in it sees it in their Messages; nothing is emailed and no notification is written. Returns: The message.

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>",
      "conversation": "<conversation>",
      "body": "<body>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe message.
campaignYesThe campaign, by its slug (what its link says) or its id.
conversationYesThe conversation's id, or `table` for the Game Master thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the authorization rule, the visibility model ("everybody else in it sees it in their Messages"), and the absence of side channels ("nothing is emailed and no notification is written"). Annotations only say it is a non-destructive, non-idempotent, non-open-world write — the description supplies the operational consequences an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: capability first, permission constraint second, side effects third, return value last. No filler and nothing buried.

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?

For a three-parameter write tool with no output schema, the description covers authorization, visibility, notification behavior, body syntax, and the return value. Nothing an agent needs 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a syntax rule not present in the schema: `[[Name]]` in the body links a wiki page. That is genuine meaning beyond the schema, lifted one point.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Write in a conversation") and immediately scopes it against siblings: this posts into an existing conversation, unlike start_conversation or read_conversation. The special-case conversation `table` (Game Master thread) is named explicitly, which an agent could not infer from the schema alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear permission context: anyone in a direct conversation may post, but only the GM posts in the `table` thread — a real selection constraint. It does not explicitly name alternatives (e.g., start_conversation for new threads), but the permission model and thread restriction make the when-to-use boundary clear.

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