Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

Add a note to a session

add_session_note

Write a shared note on a play date. Wrap a name in [[double brackets]] to link it to its wiki page (a page is made if none exists). The GM's note on a new date logs the session too; a player can only write on a date the GM has logged. The GM's first note on a session emails the other seats a link to it (never the notes), unless the table or the seat has switched those letters off. Returns: The note's id.

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>",
      "date": "<date>",
      "body": "<body>"
    },
    "name": "add_session_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe note, in the journal's markdown.
dateYesThe play date, YYYY-MM-DD. A session's date is its address.
campaignYesThe campaign, by its slug (what its link says) or its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare it is a non-idempotent write; the description adds the consequential behavior an agent cannot infer: wiki pages are auto-created from [[brackets]], the GM's note on a new date logs the session, and the first GM note emails other seats a link (never the note body) subject to per-table/per-seat opt-outs. It also states the return value, which matters since there is no 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?

Four tight sentences, front-loaded with the action, then link syntax, then permission/side-effect rules, then the return value; every sentence carries information. The phrasing "switched those letters off" is slightly idiomatic where "opted out of notification emails" would be unambiguous.

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 3-required-parameter write tool with no output schema, the description covers side effects, permission gating, notification conditions, and the return value. An agent has everything needed to decide whether the call will succeed and what it will produce.

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 campaign slug/id, date format, and markdown body are already documented in the schema. The description reinforces the date-as-session-address semantics through the GM-logging rule but adds no new syntax or format guidance. Baseline 3 is appropriate.

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 a shared note on a play date") and the qualifier "shared" plus the GM/player framing separates it from personal-note siblings like create_my_note and update_session_note. An agent can tell what this creates and who it belongs to without opening the schema.

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 concrete conditional usage: a GM's note on a new date also logs the session, and a player may only write on a date the GM has already logged. That is real when-you-can-use guidance tied to role and state. It stops short of naming an alternative tool (e.g. update_session_note) for editing an existing note, so it is not a full routing statement.

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