Skip to main content
Glama

Wait a bounded time for the current stage to settle (read-only)

dsh_wait_task
Read-onlyIdempotent

Blocks briefly until the delegated task's current stage ends, then returns its latest status so you can poll again. Timeouts are never treated as failures.

Instructions

Blocks up to timeoutMs (default 30000, hard cap 120000 = limits.waitTimeoutMaxMs in dsh_get_capabilities) waiting for the current stage to end. On timeout it returns the latest status and says you may simply call it again. It never waits indefinitely and never treats a timeout as failure. IMPORTANT for clients: set your own per-request timeout above limits.clientRequestTimeoutFloorMs (125000ms); an MCP client's SDK default is 60s, so a long wait will otherwise be aborted client-side and look like a transport failure.

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

Input Schema

NameRequiredDescriptionDefault
taskIdYes
timeoutMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the blocking semantics, timeout-vs-failure distinction, retry pattern, and a critical client-side caveat that SDK default timeouts of 60s will abort a long wait and masquerade as a transport failure. That is exactly the non-obvious operational context an agent needs and cannot get from structured fields.

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?

The bounds are front-loaded, every sentence carries distinct information (bound, timeout behavior, retry guidance, client timeout floor), and there is no filler or repetition.

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 two-parameter read-only tool with no output schema, the description covers the semantics, limits, and failure modes thoroughly, including what a timeout returns. It is slightly thin on what a successful return looks like (settled status payload), but that is a minor omission.

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 description coverage is 0%, so the description must carry the parameters, and it does so well for timeoutMs: default 30000, hard cap 120000, and a pointer to limits.waitTimeoutMaxMs in dsh_get_capabilities. taskId is left unexplained beyond the implicit 'current stage', which is the one remaining gap.

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?

The description states a specific verb and scope: it blocks for a bounded time waiting for 'the current stage to end', with explicit default and cap values. It is clearly a blocking wait rather than a poll, but it never names or contrasts a sibling (e.g. dsh_get_task) to nail down the distinction.

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?

It gives clear operating context: call it to wait for stage completion, call it again after a timeout, and never interpret a timeout as failure. It does not explicitly say when a plain status poll is preferable to blocking, so the alternative-selection rule is implied rather than stated.

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