droid-mcp

droid_wait

Read-only

Follow a session by returning new events after a sequence number, waiting up to a set time for activity; omit the sequence to fetch the latest events immediately.

Instructions

Follow a session: returns new events after afterSeq, waiting up to waitMs (max 50000) for something to happen. Without afterSeq, returns the latest events at once. Use nextSeq as the next afterSeq.

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": {
      "session": "<session>"
    },
    "name": "droid_wait"
  }
}

Input Schema

Name	Required	Description	Default
`waitMs`	No
`session`	Yes
`afterSeq`	No
`maxEvents`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

readOnlyHint=true is consistent with a read-only follow operation. Beyond the annotation, the description discloses genuinely non-obvious behavior: the call can block, the wait is capped at 50000 ms, and omitting afterSeq makes it non-blocking. It does not say what happens on timeout with no events or whether the stream ever terminates.

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?

Two compact sentences, front-loaded with the long-poll mechanic, with no filler. Minor cost: the duplicated word in "after afterSeq" and the fact that the return-contract hint (use nextSeq as next afterSeq) is tacked on at the end.

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?

With no output schema, the description must explain the return contract, and it only partly does: nextSeq is covered, but the events payload, ordering, and timeout behavior are not, and two of four parameters go undocumented. Adequate for a long-poll tool, but not complete.

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 description coverage is 0%, so the description carries the full burden. It explains afterSeq and waitMs (including the 50000 cap) but says nothing about the required session parameter or maxEvents, whose 1-200 bounds are only visible in the raw schema.

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?

States a specific verb and resource: follow a session by returning new events after afterSeq, blocking up to waitMs. That distinguishes it from a plain result-fetch sibling, but the description never names an alternative, so an agent must infer the boundary itself.

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 clear operating context: supply afterSeq to resume from a cursor, omit it to fetch the latest events immediately, and feed nextSeq back in as the following afterSeq. It stops short of saying when this tool is preferable to the sibling result/find tools, so 4 rather than 5.

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

Deploy Server