Skip to main content
Glama

read_events

Fetch persisted execution events for a run from a monotonic cursor to track progress and retrieve only new updates.

Instructions

Read persisted execution events using a monotonic cursor.

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": {
      "run_id": "<run_id>"
    },
    "name": "read_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
run_idYes
after_sequenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it omits key traits: whether the call blocks or returns immediately, ordering and retention guarantees of the event log, whether events can be missed, and any limit ceiling. "Persisted" hints at durable storage but does not specify what that means operationally.

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 verb and resource come first. Its brevity is efficient, though it borders on under-specification for a paged read API.

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

Completeness2/5

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

No output schema, no annotations, and 0% parameter documentation means the description is the agent's only source of truth, and it explains neither the returned event shape nor pagination behavior. For a cursor-paged read tool this leaves the caller guessing on termination and resume semantics.

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 description coverage is 0% across three parameters, so the description must compensate and largely doesn't. The cursor phrase loosely maps to after_sequence, but run_id (the required parameter) and limit (including its default and maximum) receive no explanation of meaning or format.

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?

"Read persisted execution events" gives a specific verb plus resource, and "using a monotonic cursor" narrows it to incremental/tail-style reads. It never distinguishes itself from siblings like get_run or get_artifacts, so the agent must infer which read surface to pick.

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 statement of when to call this versus get_run/get_artifacts, no mention of polling vs one-shot reads, and no prerequisites such as whether the run must be finished. The only implicit hint is the cursor wording, which weakly suggests incremental consumption.

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