Skip to main content
Glama

rex_events_poll

Poll buffered Rex server events from a cursor to retrieve new events and the next cursor; use the dropped flag to detect when events fell out of the buffer.

Instructions

Long-poll buffered Rex server events after cursor (0 = oldest). Returns events and the next cursor; dropped: true means events after your cursor fell out of the buffer.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
typesNoMatch the event type or a session_event's inner type
cursorNo
sessionNoSession label or ID
wait_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses blocking long-poll behaviour, the buffer-overflow signalling through `dropped: true`, and the shape of the return (events plus next cursor). It omits auth/permission needs and what happens when `wait_ms` is defaulted, which is the main remaining gap.

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?

Two dense sentences, front-loaded with the core action and immediately followed by the return and error-signalling contract. No filler, and each clause carries information an agent needs to run the poll loop.

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 five-parameter polling tool with no annotations and no output schema, the description covers the critical contract: what triggers a return, what comes back, and how to detect a lost buffer. It falls short on defaults (notably what happens when `wait_ms` is omitted) and on filtering parameters, but is largely complete for correct invocation.

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 only 40%, so the description must compensate; it documents `cursor` semantics ('0 = oldest'), which is genuinely useful information beyond the schema. It says nothing about `wait_ms`, `limit`, or `session`, leaving three of five parameters unexplained in either place.

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 and resource ('Long-poll buffered Rex server events') plus cursor semantics, which is far more concrete than a name restatement. It does not name any sibling, so an agent must infer for itself why it would pick this over `rex_wait` or `rex_status`, but the purpose is unmistakable.

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?

The description implies the polling loop via 'after `cursor` (0 = oldest)' and the next-cursor return, which tells an agent how to iterate. It never says when to use this instead of `rex_wait` or `rex_status`, and gives no exclusions or prerequisites, so the guidance remains implicit.

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