Skip to main content
Glama

body_events

Read the real execution event stream from the executor to report what actually happened and detect when the user must act, such as approvals, CAPTCHAs, or logins.

Instructions

Read the real execution event stream (task lifecycle, actions, verifications, blockers).

Events are emitted by the executor itself, not by the model. Use it to report what actually happened, and to notice when the user must act (approval, CAPTCHA, login).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does add notable behavioral context: the events originate from the executor rather than the model, so they represent ground truth, and the stream surfaces user-action-required states. It omits whether reads are snapshot or incremental, whether calls block or poll, and how much history is retained.

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?

Three short sentences, front-loaded with the core action, each carrying distinct information (what it reads, where the data comes from, why to use it). No filler or restatement of the name.

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

Completeness3/5

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

For a two-parameter, no-annotation, no-output-schema read tool, the description explains the nature and value of the data but leaves the parameter semantics and return shape (event fields, ordering, pagination behavior) entirely unaddressed. Adequate for understanding intent, insufficient for precise invocation.

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% — 'limit' and 'since' appear with only types and defaults. The description says nothing about either parameter: no meaning for 'since' (timestamp? event index?), no default or range guidance for 'limit'. The burden to compensate is not met.

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 names a specific verb and resource ('Read the real execution event stream') and enumerates its contents (task lifecycle, actions, verifications, blockers), which is far more specific than the bare name. It stops short of distinguishing itself from sibling status/report tools like body_task_status or body_workflow_report.

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?

'Use it to report what actually happened, and to notice when the user must act (approval, CAPTCHA, login)' gives a clear usage context, but there is no explicit exclusion or alternative named among the many status/report siblings. An agent must infer when to prefer this over body_status or body_task_status.

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