Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Edit a session note

update_session_note
Idempotent

Rewrite a shared note. Your own, or any if you are the GM. Every version is kept. Returns: { ok: true }.

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>",
      "note": "<note>",
      "body": "<body>"
    },
    "name": "update_session_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe whole note, as it should now read.
noteYesThe note's 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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, so the description's real contribution is the authorization model (own note, or anyone's as GM) and the versioning guarantee ('Every version is kept'), which tells the agent edits are recoverable. It also discloses the return payload even without an output schema; only the full-overwrite semantics of 'body' go unstated as a behavior caveat.

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?

Four short sentences, zero filler, with the mutating action and the permission scope front-loaded before the durability note and return value.

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 small 3-parameter mutation with full schema coverage, the description covers permission, reversibility, and return shape. The one gap is that a whole-note overwrite is not explicitly framed as replacing prior content, which is the main thing an agent must not get wrong.

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 three parameters are already documented, including that body is 'the whole note, as it should now read'. The description adds no format or resolution detail beyond the schema, 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?

States a specific verb ('Rewrite') and resource ('a shared note'), which separates it from the note-creation and wiki-editing siblings. It does not name the closest alternative (update_my_note / add_session_note), so the reader must infer the 'shared vs my note' boundary.

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?

'Your own, or any if you are the GM' gives a clear permission precondition for when this call will succeed. It stops short of saying when to choose this over update_my_note or add_session_note, so the alternative selection is only implied.

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