Skip to main content
Glama
thyn-ai

Algenta MCP

Official
by thyn-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_agent_run_events

Read-onlyIdempotent

Fetch the ordered event stream for an agent run, covering creation, tool activity, completion, and pause/approve/cancel transitions, to review or replay its execution history.

Instructions

Fetch the append-only event stream of one agent run — run_created, tool_selected, tool_executed, run_completed, and the pause/approve/cancel transitions — in order. Use get_agent_run_mission_events for the canonical mission-event projection of the same trail. Read-only; an unknown run_id fails with agent_run_not_found. Returns data plus total_events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum events returned, up to 1000; defaults to 1000.
run_idYesRun id returned by create_agent_run or list_agent_runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • addedInput schema / properties / limit / description
      Added value: +"Maximum events returned, up to 1000; defaults to 1000."
    • addedInput schema / properties / run_id / description
      Added value: +"Run id returned by create_agent_run or list_agent_runs."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint, and the description adds further behavioral detail: append-only semantics, event ordering, specific failure behavior, and the return summary. No contradiction with 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?

Three dense sentences with no filler. The core purpose is front-loaded, and each clause adds value: event types, ordering, alternative tool, read-only status, failure behavior, and return shape.

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

Completeness5/5

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

For a two-parameter read tool with strong annotations, the description provides everything needed: event domain, ordering, relation to the sibling tool, failure mode, and return summary. The lack of an output schema is mitigated by the explicit return description.

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%, and the schema already explains run_id provenance and limit defaults. The description adds error behavior tied to run_id, but no new parameter format or semantics, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Fetch the append-only event stream of one agent run'. It enumerates the event types, states ordering, and explicitly distinguishes the tool from get_agent_run_mission_events, making selection unambiguous.

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

Usage Guidelines5/5

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

The description explicitly routes to the sibling tool for the canonical mission-event projection, which clarifies when not to use this tool. It also states the read-only nature and the failure mode for unknown run_id.

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