wait_for_responses
Wait for human responses to a submitted query, blocking up to 50 seconds to collect enough answers, returning a complete result or a pending status to continue waiting.
Instructions
Poll for human responses to a query, blocking for up to max_wait_seconds (default 50, max 50) before returning. Use right after submit_query to wait for real answers in one call instead of manually re-checking with get_responses. DOES NOT GUARANTEE COMPLETION -- if min_responses have not arrived within the time budget it returns status "pending" (with a hint to call again) rather than erroring; call again to keep waiting. Returns status "ready" with the responses array once enough have arrived (or the query otherwise completed). Read-only / free -- cost was already charged by submit_query. Disambiguation: unlike get_responses (instant, one-shot, may return 0 responses), this actively waits, trading time for a higher chance of a complete result.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query_id | Yes | The id returned by submit_query, identifying which query to wait on. | |
| min_responses | No | How many responses must arrive before returning status "ready" (default: the query's required_responses). | |
| max_wait_seconds | No | Maximum seconds to poll before giving up and returning status "pending" if not enough responses arrived yet (default 50, max 50). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hint | No | ||
| status | No | ||
| responses | No | ||
| required_responses | No | ||
| completed_responses | No |