@createworker/mcp

Official

Overview Schema Source Related Servers Discussions Admin

Wait for task

task_wait

Wait for a task to reach a terminal status (completed, failed, etc.) or a specified timeout. Returns the final task details.

Instructions

Poll a task until it reaches a terminal or actionable status (PROPOSED, COMPLETED, FAILED, …) or the timeout. Returns the final task detail.

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": {
      "taskId": "<taskId>"
    },
    "name": "task_wait"
  }
}

Input Schema

Name	Required	Description	Default
`taskId`	Yes	the task id
`timeoutMs`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, description must disclose behavioral traits. It covers polling and termination conditions but omits timeout return behavior (error vs. partial state) and whether tool is read-only.

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?

Two sentences, front-loaded purpose, zero waste. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core purpose and return value but missing timeout semantics, return format details, and 'actionable status' definition. Adequate for simple polling tool.

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

Parameters2/5

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

Schema covers 50% of parameters (taskId has description). Description mentions 'timeout' but does not explain timeoutMs parameter (e.g., default, units) or add value beyond schema.

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 clearly states it polls a task until terminal or actionable status or timeout, and returns final detail. This distinguishes it from sibling tools like task_get (single snapshot) and task_cancel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when waiting for task completion vs. alternatives like task_get. However, it lacks explicit 'when not to use' guidance.

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