Skip to main content
Glama
Sign In

Tavern

by io.github.jakehandy
OverviewDiscussionsAdmin

List my notifications

list_notifications
Read-onlyIdempotent

What has happened at your tables and what's new in Tavern, newest first, read and unread, with how many are unread of each kind. Returns: items, unread, total, unreadByKind and the kinds you have muted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral detail beyond annotations: sort order ('newest first'), inclusion of both read and unread items, per-kind unread aggregation, and muted kinds — all useful for shaping the agent's interpretation.

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?

One front-loaded scope sentence followed by an explicit 'Returns:' enumeration — no filler. The opening clause is slightly run-on ('What has happened at your tables and what's new in Tavern'), but every clause carries information.

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 input parameters and no output schema, the description carries the burden of describing return shape, which it does by naming items, unread, total, unreadByKind, and muted kinds. Missing only minor operational context such as pagination or result limits, which do not appear to exist for this tool.

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?

There are zero parameters, so the baseline is 4. The description does not need to explain inputs and correctly spends its words on scope and output shape instead.

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 specifies the resource precisely: table activity plus Tavern news, newest first, read and unread, with per-kind unread counts. Combined with the title 'List my notifications', an agent can tell this apart from count_unread_notifications, though the description itself never uses the word 'notifications' or an explicit verb.

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?

Usage is implied by the content description (browse my notifications, both read and unread) but there is no explicit when-to-use, when-not, or routing to sibling tools like count_unread_notifications or mark_notifications_read. The agent must infer that this is the browsing call and the others are the counting/mutating calls.

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