Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_loop_events

Read-only

Polls a manager loop session incrementally for events after a given sequence number, returning bounded results plus any in-progress streamed text for display.

Instructions

MANAGER READ: bounded session events, for incremental client polling.

Events with seq greater than after_seq, bounded to limit, and partial: the running turn's streamed, unfinished text for this session, or null. The partial is display only; it is never persisted or sent to a model.

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": {
      "session_id": "<session_id>"
    },
    "name": "aiworkhub_manager_loop_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum events to return; default 200.
after_seqNoReturn only events whose seq is greater than this value; default 0 starts from the first event. Pass the last seq already seen to poll incrementally.
session_idYesId of the manager loop session to read, as returned by aiworkhub_manager_loop_status.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.67
    • addedInput schema / properties / after_seq / description
      Added value: +"Return only events whose seq is greater than this value; default 0 starts from the first event. Pass the last seq already seen to poll incrementally."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum events to return; default 200."
    • addedInput schema / properties / session_id / description
      Added value: +"Id of the manager loop session to read, as returned by aiworkhub_manager_loop_status."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as read-only and closed-world, and the description adds useful behavior: events are bounded by seq and limit, and the partial field is display-only and never persisted or sent to a model. That is meaningful context beyond the annotations.

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?

The description is short, front-loaded, and wastes no sentences. It introduces the operation, polling usage, and the partial-output caveat efficiently.

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?

Given full parameter documentation, existing annotations, and an output schema, the description supplies enough context for correct invocation. It could be slightly richer about event ordering or polling behavior, but the essential caveats are present.

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 100%, so the parameter meanings are already well documented. The description reinforces the seq-greater-than-after_seq and limit-bounded semantics but does not add much parameter detail beyond the schema.

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 states a specific operation: reading bounded session events for incremental polling. It clearly distinguishes the resource and intended mode from generic session status tools, though it does not explicitly name a sibling alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear usage context: incremental client polling of session events. It lacks explicit when-not-to-use guidance or named alternatives such as loop_status, but the polling context is clear enough for an agent to choose it appropriately.

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

Deploy Server

Other Tools