Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Read a conversation

read_conversation
Read-onlyIdempotent

A conversation's messages, oldest first, written in the journal's dialect ([[Name]] links a wiki page). table names the Game Master thread. Page back with before; ask for only what is new with after. Returns: thread, messages and whether there are more older ones.

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

Input Schema

NameRequiredDescriptionDefault
afterNoOnly messages written after this time (ISO 8601).
beforeNoOnly messages written before this time (ISO 8601).
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

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive semantics, so the bar is lower. The description adds real context beyond them: messages are written in the journal's dialect, `[[Name]]` denotes a wiki link, `table` is the Game Master thread, and it discloses the return shape including the `more` flag. It omits page-size limits and default behavior when neither cursor is given.

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 tight sentences with no filler, leading with what is returned before pagination notes. The telegraphic style ('A conversation's messages, oldest first') borders on terse but remains parseable, and nothing is wasted.

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?

With no output schema, the description usefully names the returned fields (thread, messages, more) and explains ordering and dialect conventions. It lacks details on default page size, maximum limits, and behavior when cursors are omitted, which would matter for a paginated read.

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 schema already documents each parameter's type and format. The description still adds intent: `before` is for paging backwards through history and `after` is for incremental fetching, and it reinforces that `table` selects the GM thread. That is meaningful beyond the raw ISO 8601 field docs.

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 states the specific resource and contents ('a conversation's messages, oldest first') so the agent knows exactly what is returned. It implicitly distinguishes itself from list_conversations by returning messages rather than conversation metadata, but never names that sibling explicitly.

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?

It explains pagination behavior ('page back with before', 'only what is new with after'), which is practical usage guidance. However, it offers no explicit routing against siblings like list_conversations or mark_conversation_read, and no statement of when not to use it.

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