Skip to main content
Glama

Wait for execution

wait_for_execution
Read-only

Block for up to timeout_seconds (default 45, maximum 50) until a platform execution reaches a terminal status, then return the same document get_execution_details returns plus waited_seconds and timed_out. Built for stateless clients such as MCP, whose calls have a 55-second deadline and no durable park: after a mutating tool answers with an operation_id or live_status_hint, call this once or twice instead of polling get_execution_details in a tight loop. timed_out true means the execution is still running - call again, or stop and report the last observed step summary. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "execution_id": "<execution_id>",
      "cluster_id": "<cluster_id>"
    },
    "name": "wait_for_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
execution_idYesThe UUID of the execution to wait for.
timeout_secondsNoHow long to wait before answering with timed_out true. Defaults to 45.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true; the description adds the substantive behavior: it blocks, default 45s and max 50s, the 55-second client deadline that motivates the cap, the extra waited_seconds and timed_out fields in the response, and the meaning of timed_out=true. Its 'Read-only' statement is consistent with the annotation rather than contradicting it.

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 plus a two-word safety tag, front-loaded with the blocking behavior and the timeout limits before the usage rationale. Nothing is padding: each clause either constrains the call, explains the cap, or tells the agent what to do on timeout.

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?

No output schema exists, but the description names the return payload relative to a known sibling and flags the two added fields, so the agent knows what comes back. Combined with the timeout semantics and the deadline rationale, an agent has everything needed to call this correctly and interpret the result.

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 parameters are already documented; the description adds the rationale behind the maximum (the 55-second call deadline) and ties timeout_seconds to the timed_out result. It does not add much on execution_id or cluster_id beyond the schema, so it sits just above the baseline rather than fully exceeding it.

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 ('block ... until a platform execution reaches a terminal status') and pins down the return value ('same document get_execution_details returns plus waited_seconds and timed_out'). It also explicitly distinguishes itself from the sibling get_execution_details by framing itself as the alternative to tight-loop polling.

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?

Gives explicit when-to-use: after a mutating tool answers with an operation_id or live_status_hint, call once or twice instead of polling get_execution_details. It also gives when-to-stop guidance for the timed_out case ('call again, or stop and report the last observed step summary'), which is the exact decision point an agent faces.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.