Skip to main content
Glama

Wait for a DSH task

dsh_wait

Waits for the current turn of a DSH session to finish, up to 30 seconds. If time runs out, returns running status with partial output; call again with the same sessionId to continue waiting.

Instructions

Wait up to 30 seconds for the current turn of a DSH session to finish. Returns status "running" with partial output when the budget elapses; call again with the same sessionId.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "dsh_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesDSH session id, e.g. session-… returned by a previous call.
timeoutMsNoWait budget in milliseconds; capped at 30 seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it states the wait ceiling, the exact timeout return condition ('running' with partial output), and the required retry protocol. The gap is that the success branch is never described — what is returned when the turn actually finishes — and there is no mention of whether the wait blocks resources or how repeated calls are counted.

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, no padding, and the primary behavior (bounded wait) is front-loaded ahead of the timeout branch and retry instruction. Every clause carries information an agent needs.

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 polling tool with no output schema, the description covers the core contract: bound, timeout return value, and retry semantics. It is slightly incomplete in omitting the completed-turn return shape, which the absence of an output schema would otherwise require the prose to supply.

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 100%, so both parameters are already documented, making 3 the baseline. The description adds only mild meaning — the default/effective 30-second budget and the requirement to reuse the same sessionId across calls — with no format or edge-case detail about timeoutMs beyond the schema's min/max.

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?

Names a specific verb and resource ('Wait ... for the current turn of a DSH session to finish') plus the 30-second bound, which is enough to distinguish it from the sibling set (dsh_run, dsh_get, dsh_info). It stops short of explicitly contrasting itself with a status-check sibling such as dsh_get, so it is clear but not maximally differentiated.

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?

Gives concrete usage context: it is a bounded wait for the current turn, and if the budget elapses the caller should 'call again with the same sessionId', which defines the polling loop. No explicit when-not or named alternative is given, so it clears the 'clear context, no exclusions' bar rather than the top tier.

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