Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Stream Run Events (beta)

alterlab_run_stream
Read-onlyIdempotent

Read a run's progress events in order (beta feature). Events such as step.started, step.completed, budget.warning and run.succeeded in seq order. The call returns once the run is finished and drained or the server closes the stream. Pass last_event_id from a previous call to receive only newer events. Returns events, last_event_id and truncated.

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

Input Schema

NameRequiredDescriptionDefault
run_idYesRun id returned by alterlab_run_create
max_eventsNoMaximum events to return (default 100)
last_event_idNoReturn only events after this seq

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely useful behavior the annotations cannot express: the call blocks until the run finishes and is drained or the server closes the stream, and it supports incremental resumption via last_event_id. It stops short of covering failure modes such as unknown run_id or what 'truncated' means in practice.

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?

Four short sentences, front-loaded with the purpose, then event types, then blocking semantics, then the resume tip. No filler; the only minor redundancy is 'in order' followed by 'in seq order', which is negligible.

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 output schema, the description compensates by naming the return fields (events, last_event_id, truncated), which is exactly what an agent needs. Combined with the 100% schema coverage and the disclosed blocking behavior, the definition is nearly sufficient; error/edge-case behavior is the main remaining gap.

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 coverage is 100%, so run_id and max_events are already documented and the baseline applies. The description adds only modest meaning to last_event_id by framing it as a resume cursor ('only newer events'), while max_events is never mentioned in the description.

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 gives a specific verb and resource ('Read a run's progress events') plus concrete event names (step.started, step.completed, budget.warning, run.succeeded), which lets an agent distinguish it from alterlab_run_result and alterlab_run_create without opening the schema. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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?

It implies the streaming/polling use case and explains the resume pattern ('Pass last_event_id from a previous call to receive only newer events'), but there is no explicit statement of when to use this versus alterlab_run_result or how to handle a run that has not yet started. Usage is inferable rather than prescribed.

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

All mcp-server 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