Skip to main content
Glama
thyn-ai

Algenta MCP

Official
by thyn-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_agent_runs

Read-onlyIdempotent

Find and list persisted agent runs with filters for status, request hash, policy snapshot, or schema snapshot. Paginated read-only access returns run details, totals, and page info.

Instructions

List the organization's persisted agent runs, paginated (defaults page 1, limit 25), with lineage-aware filters: status, request_hash (find reruns of the same request), policy_snapshot_id, and schema_snapshot_id (find runs under one policy or schema revision). Use get_agent_run for one run's full detail and query_agent_run_checkpoints to search checkpoints across runs. Read-only. Returns data, total, page, limit, and pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number; defaults to 1.
limitNoRuns per page, up to 200; defaults to 25.
statusNoKeep only runs in this lifecycle status.
request_hashNoKeep only runs created from this request hash.
policy_snapshot_idNoKeep only runs under this execution-policy snapshot.
schema_snapshot_idNoKeep only runs under this schema snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.3
    • addedInput schema / properties / limit / description
      Added value: +"Runs per page, up to 200; defaults to 25."
    • addedInput schema / properties / page / description
      Added value: +"1-based page number; defaults to 1."
    • addedInput schema / properties / policy_snapshot_id / description
      Added value: +"Keep only runs under this execution-policy snapshot."
    • addedInput schema / properties / request_hash / description
      Added value: +"Keep only runs created from this request hash."
    • addedInput schema / properties / schema_snapshot_id / description
      Added value: +"Keep only runs under this schema snapshot."
    • addedInput schema / properties / status / description
      Added value: +"Keep only runs in this lifecycle status."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavior details: pagination defaults, lineage-aware filtering, and the exact return fields (data, total, page, limit, pages). This exceeds the minimum expected given 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 dense but well-organized: purpose and pagination first, then filters, then sibling routing, then return shape. Every sentence adds unique information with no filler or redundancy.

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?

Given six flexible parameters and no output schema, the description covers all essential call decisions: default pagination, filter semantics, sibling alternatives, read-only nature, and exact response fields. An agent can invoke this tool correctly without additional information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented. The description adds value by explaining the intent behind request_hash ('find reruns of the same request') and snapshot IDs ('find runs under one policy or schema revision'), which helps an agent choose the right filter.

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?

Description clearly states the tool lists the organization's persisted agent runs with pagination and lineage-aware filters. It explicitly differentiates from get_agent_run and query_agent_run_checkpoints by naming them and their distinct purposes.

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?

Provides explicit routing guidance: 'Use get_agent_run for one run's full detail and query_agent_run_checkpoints to search checkpoints across runs.' This makes the choice between siblings unambiguous and gives context for filter usage.

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