Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

List my private notes

list_my_notes
Read-onlyIdempotent

Your own sealed notes at this table: scratch notes, and the ones filed on a play date or a wiki page. Nobody else can read these, the GM included. Returns: Your notes.

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

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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the notes are sealed and unreadable by anyone else, including the GM, which affects how an agent should frame the results. It stops short of saying anything about ordering, pagination, or result size.

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 sentences with the privacy guarantee front-loaded and no filler. The phrasing is stylized ('at this table', 'a play date') but does not obscure meaning, and the 'Returns:' line is a clean structural cue.

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 single-parameter, read-only list tool with full annotation coverage, the description supplies what is missing from structured data: the privacy scope and the kinds of notes included. The main residual gap is the absence of any pointer to the sibling tools that list overlapping content.

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 already explains that it accepts a slug or an id. The description adds no parameter-level meaning 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.

Purpose4/5

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

The description clearly defines the resource and its scope: the caller's own private notes tied to a campaign, split into scratch notes and notes filed on a play date or wiki page. The list verb is only implied by the name rather than stated, and no sibling (list_everything_i_wrote, get_my_note_history, list_my_private_pins) is named to sharpen the distinction.

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 explicit when-to-use guidance. The description never contrasts this with list_everything_i_wrote, get_my_note_history, or list_my_private_pins, which are close enough siblings that an agent could plausibly pick the wrong one. The only implicit guidance is the campaign scoping.

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