Skip to main content
Glama
CronusL-1141

AI Team OS

by CronusL-1141
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

workflow_get

Retrieve a workflow run's archive with totals, summary/result, and per-agent telemetry; use compact view for trimmed rows or all for full details.

Instructions

Get a Workflow run's archive (totals + summary/result + per-agent telemetry).

Default response is a COMPACT projection (view="compact" + hint - trimmed, NOT missing fields). Compact keeps every scalar on the run, excerpts its result (400 chars) and summary (200 chars), and projects the agent rows down to identity / phase / cost / state plus the os_agent_id drill-down key.

Both views keep planned_agent_count and dynamic_nodes on the run. Read them together: planned_agent_count is the static lower bound (literal agent() calls), dynamic_nodes counts runtime-width fan-out nodes, so agent_count > planned_agent_count is expected whenever dynamic_nodes > 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax agent rows to return in compact view (default 40, capped at 200)
wf_idYesWorkflow run id (e.g. "wf_8e92fe01-67c").
fieldsNo"compact" (default, trimmed rows) / "all" (full archive)compact
include_agentsNoWhen True, also fetch the per-agent telemetry rows.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max agent rows to return in compact view (default 40)"New value: +"Max agent rows to return in compact view (default 40, capped\nat 200)"
  2. Changed2 schema fields changedv1.11.2
    • addedInput schema / properties / fields
      Added value: +{
+  "default": "compact",
+  "description": "\"compact\" (default, trimmed rows) / \"all\" (full archive)",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 40,
+  "description": "Max agent rows to return in compact view (default 40)",
+  "type": "integer"
+}
  3. First observedv1.9.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the default compact projection, that trimming means excerpts not missing fields, the 400/200-char excerpt caps, which agent columns survive, and the drill-down key. It stops short of stating the read-only/safety profile or whether the archive is ever mutated, so it is strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose in sentence one, followed by two tight paragraphs on view semantics and the planned/dynamic count relationship. Dense but every sentence carries information; only minor tightening would be possible.

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?

An output schema exists, so return values need not be restated, and the description still covers view behavior, drill-down key, and count semantics well. What is missing is any note on read-only safety, auth requirements, or error behavior for an invalid wf_id.

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 the baseline is 3, but the description genuinely adds meaning beyond the schema: it clarifies that 'compact' is a projection rather than a lossy filter, spells out the excerpt lengths and retained fields, and explains the relationship between planned_agent_count and dynamic_nodes that the schema only names.

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?

States a specific verb and resource — 'Get a Workflow run's archive' — and immediately enumerates what the archive contains (totals, summary/result, per-agent telemetry). The required wf_id plus the run-scoped framing cleanly separates it from workflow_list and workflow_reconcile without ambiguity.

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?

Usage is implied (fetch one run's archive by wf_id) but the description never names alternatives such as workflow_list for enumerating runs or workflow_reconcile, nor states when-not to use this tool. The only routing guidance is internal, about how to interpret planned_agent_count vs dynamic_nodes.

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