Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

workflow_run_wait

Read-only

Wait for an async workflow run for at most 60 seconds. Use when workflow_test_run, workflow_execute, or a wf_* tool returns a run handle. Do not use when you need to start a run. Next step: if pending or running persists without progress, call workflow_execution_get_steps with executionId if available before waiting again. PENDING can include failed-step retries. Do not infer worker capacity from status alone or start duplicate runs. Limits: the server checks tenant and workflow access; waitSeconds above 60 is cut to 60. Example: {"executionId":"uuid","waitSeconds":30}.

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": {
      "executionId": "<executionId>"
    },
    "name": "workflow_run_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
executionIdYes
waitSecondsNo
timeoutSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral context beyond that: the 60-second wait cap, tenant and workflow access checks, retries counting as PENDING, and warnings against duplicate runs. It does not explain what the response looks like, but it discloses the key runtime behaviors.

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?

The description is dense but front-loads the core action, scope, and cap. It includes some operational guidance that earns its place, though the mix of next-step, warning, and limit sentences could be organized more cleanly.

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?

For a three-parameter polling tool with no output schema, the description covers the main usage context, safety constraints, and key operational caveats. The main gap is that timeoutSeconds is never explained, and return-value expectations are only implied.

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 0%, so the description needs to carry parameter meaning. It gives an example using executionId and waitSeconds and states that waitSeconds is capped at 60, but it does not explain timeoutSeconds or clarify how it differs from waitSeconds.

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 states a specific action and resource: wait for an async workflow run for at most 60 seconds. It also distinguishes the tool from starting a run, which is the key sibling distinction an agent needs.

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?

It explicitly says when to use it: after workflow_test_run, workflow_execute, or a wf_* tool returns a run handle. It also says when not to use it and gives a next-step alternative when pending or running persists.

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

All Spaces by Peakflo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources