Skip to main content
Glama

events

Read-onlyIdempotent

Read durable progress since a cursor and let a consumer resume from its unread position without marking records as read.

Instructions

Read durable progress since a cursor; optional consumer resumes its unread cursor without marking read.

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": "events"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
task_idNo
consumerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: state is durable, a cursor drives the read position, and supplying a consumer resumes its unread cursor without advancing the read pointer. It omits ordering, pagination and whether the cursor is per-consumer or global.

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?

A single front-loaded sentence with no filler; the semicolon split separates the cursor read from the consumer behavior. It is dense to the point of being cryptic, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return shape needn't be described, and annotations cover safety. Still, for a 4-parameter read tool with zero schema coverage, the definition leaves the filter ('task_id'), page size, and the exact interaction between 'after' and 'consumer' undefined.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning and it only partly does: 'since a cursor' maps loosely to 'after' and 'consumer' is named but not explained (e.g. that it overrides cursor semantics or is a namespace). 'limit' and 'task_id' are entirely unaddressed, leaving half the parameters undocumented anywhere.

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 ('Read') and resource ('durable progress since a cursor'), and the 'without marking read' clause implicitly separates it from events_ack. The word 'progress' is somewhat abstract versus the tool name 'events', but the cursor-based scope is concrete enough to select it.

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 rather than stated: read/peek at events without consuming them, vs. whatever events_ack does. No explicit 'use this when' or named alternative, so the agent must infer the comparison with events_ack from the 'without marking read' phrase alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.