Skip to main content
Glama

execution_status

Read-onlyIdempotent

Check a run's progress and health: weighted completion, blockers, checks, ETA, budget, runner health, and GitHub sync; inspect tasks, escalations, events, or restart a lost runner.

Instructions

How a heads-down run is doing. Without execution_id: every run with its status. With one, view summary (default) gives weighted completion (accepted 1, submitted 0.8, otherwise the worker's percent or 0.4), blockers, the latest checks, a rough ETA, the budget, runner health, the dashboard URL and GitHub sync health; tasks, escalations, events (since_seq, limit), budget and context are the other views. focus answers questions such as "how close is the nav?": fuzzy words and prefixes matched against task ids, titles, teams, paths and interface names ("nav" finds build-nav-bar and src/components/nav/**); an escalation id as focus picks that escalation for view context. view context returns a redacted bundle (no chat, no secrets) to pass to a format at the table. Restarts the runner of a live run that lost it.

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

Input Schema

NameRequiredDescriptionDefault
viewNosummary (default), tasks, escalations, events, budget or context.
focusNoWhat the human asked about, in their words ("the nav", "api client", a task id, or an escalation id).
limitNoHow many runs, tasks, escalations or events (default 20 runs, 50 otherwise).
since_seqNoview events: start after this sequence number (default: the latest limit events).
execution_idNoThe heads-down run (exe-…), as execute or execution_status returned it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

B3.3/5.0
Behavior2/5

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

The description is behaviorally rich — weighted completion scoring (accepted 1, submitted 0.8, else worker percent or 0.4), redaction guarantees for the context view ("no chat, no secrets"), and defaults for limit/since_seq. However, the closing sentence "Restarts the runner of a live run that lost it" describes a state-mutating recovery action while the annotations declare readOnlyHint=true and idempotentHint=true, an inconsistency that will mislead an agent about side effects.

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

Conciseness3/5

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

Almost every clause carries information, but it is delivered as one long semicolon-chained block with shifting subjects (views, focus, context redaction, runner restart), and the most consequential fact — a side effect — is buried in the last sentence. Front-loading is partial: the no-id/with-id split comes early, but the view catalogue and focus semantics are tangled together.

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?

With no output schema and five optional parameters, the description does the heavy lifting well by enumerating what each view returns (weighted completion, blockers, checks, ETA, budget, runner health, dashboard URL, sync health) and by stating defaults. The remaining gap is the runner-restart behavior: no conditions, preconditions, or outcome are given, which matters for a tool otherwise advertised as read-only.

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 already 100%, so the baseline is 3, but the description adds genuine meaning beyond it: focus is fuzzy-matched against task ids, titles, teams, paths and interface names with a worked example ("nav" → build-nav-bar, src/components/nav/**), and an escalation id passed as focus scopes the view context. It also ties since_seq/limit to specific views; only the execution_id format is left entirely to 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?

"How a heads-down run is doing" plus the explicit list of views makes it clear this retrieves the status/state of a run (exe-…), and the no-id branch states it also lists all runs. The verb is implicit ("status") rather than stated, and no sibling such as control_execution is named to sharpen the boundary, so it stops short of a 5.

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?

It does give real routing guidance on parameter combinations (no execution_id → all runs with status; with one → summary by default, otherwise one of five views) and explains when to reach for focus ("how close is the nav?"). But it never says when not to use this tool or how it relates to siblings like control_execution, await_subtasks or execute, so the when-to-use picture is only implied.

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