Reads a bounded window of ARTEX Server-Sent Events, returning event IDs and an available log since a cursor so agents can monitor or resume event streams.
Read a bounded window of ARTEX SSE. Returns event IDs and a log since cursor when available.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | ||
| route | Yes | ||
| seconds | No | ||
| max_events | No | ||
| path_params | No | ||
| last_event_id | No | ||
| event_preview_chars | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it returns event IDs and a log since a cursor when available, but it does not explain blocking behavior, SSE streaming semantics, or how the bounded window behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two compact sentences with the core purpose front-loaded and no filler. However, the terseness leaves no structure for the complex seven-parameter surface.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has high complexity: seven parameters, no schema descriptions, and no output schema. The description states a minimal purpose and return hint but omits essential details about route construction, cursor semantics, window sizing, and preview limits, making it inadequate for reliable invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are seven parameters with 0% schema description coverage, so the description must carry the burden of explaining them. It only hints at a cursor and a bounded window, without naming required 'route', 'query', 'path_params', 'seconds', 'max_events', 'last_event_id', or 'event_preview_chars' or explaining their formats.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb, 'Read', and a bounded resource, 'ARTEX SSE', so the agent can identify this as an event-reading tool. It does not explicitly distinguish itself from siblings such as artex_call or artex_status, but the purpose is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says it reads a bounded window of SSE and mentions cursor availability, but it does not say when to use this instead of related tools like artex_call. There are no exclusions, prerequisites, or alternative-selection guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.