Skip to main content
Glama

dsh_team_wait

Read-only

Waits synchronously for team events like task completion, blockers, errors, authorization needs, or integration readiness while buffering routine messages; omit timeout for normal 25-minute waits.

Instructions

Quiet synchronous event wait. Normal waiting MUST omit timeoutMs: default 25 min (1500000 ms). Never routinely pass 60000; short explicit waits only for diagnostics, nonblocking checks or user request. Results distinguish requested_timeout_ms (null=omitted), effective_timeout_ms and recommended_next_wait_ms. Max 1 h; managed timeout 3900 s. Task completion, key blockers/errors/authorization and integration readiness wake early; routine messages only buffer. No MCP progress chatter or model calls. If a wrapper yields, resume that wait with its longest blocking interval, without narration. Timeout with no necessary action: immediately wait again using after=nextCursor and afterWake=nextWakeCursor. First-round readiness hands integration to Codex. Cancellation releases only the wait; timeoutMs=0 pages events, wakeEvents bypass filters/limit.

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": {
      "teamId": "<teamId>"
    },
    "name": "dsh_team_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
kindsNo
limitNo
teamIdYes
waitIdNo
afterWakeNoExplicit acknowledgement of prior nextWakeCursor; keep after=nextCursor for lossless routine-event paging.
timeoutMsNoOmit for normal waiting: default 1500000 ms (25 min). Explicit short waits only for diagnostics, nonblocking checks or user request; never routine polling.
cancelWaitIdNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0-rc.8

TDQS

B3.3/5.0
Behavior4/5

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

Goes well past the readOnly/non-destructive annotations: discloses the 25 min default, the 1 h cap, which events wake early vs. buffer, that cancellation releases only the wait, and that timeoutMs=0 pages events. The dense operational directives (wrapper yield handling, "First-round readiness hands integration to Codex") are agent-policy content whose meaning is not derivable, but the blocking semantics themselves are well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded only in the first fragment; the remainder is a run-on sequence of sentence fragments mixing timeout policy, cursor recovery, result-field semantics and unrelated agent directives. Several clauses ("without narration", "hands integration to Codex") do not earn their place in a tool definition.

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?

An output schema exists, so return-value explanation is optional and partially given (requested/effective timeout, nextCursor/nextWakeCursor). Still, for an 8-parameter tool with 25% schema coverage, the roles of waitId vs cancelWaitId and the kinds filter are left unexplained, and the phantom "wakeEvents" reference is a hazard.

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?

With only 25% schema coverage across 8 parameters, the description compensates for timeoutMs (thoroughly), after/afterWake (cursor paging) and limit. It says nothing about teamId, waitId, cancelWaitId, or the kinds enum values, and it references "wakeEvents", which does not exist in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Quiet synchronous event wait" names a blocking wait but never plainly states the resource: an agent must infer from later clauses ("task completion... wake early", "routine messages only buffer") that this streams team events for teamId. No sibling differentiation from dsh_team or dsh_delegate_task is given.

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?

Explicit when-to-use and when-not: "Normal waiting MUST omit timeoutMs", "Never routinely pass 60000; short explicit waits only for diagnostics, nonblocking checks or user request", plus recovery guidance on timeout ("immediately wait again using after=nextCursor"). It stops short of naming any alternative tool for non-blocking polling.

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

Deploy Server

Other Tools