Skip to content

elicit_await

Block until an approval request is decided, or the wait bound elapses — the long-poll at the heart of the Approval Flow.

The agent has nothing useful to do until the human decides. One elicit_await loop replaces a busy elicit_status poll: each call parks server-side and returns the instant a decision lands (or the bound elapses).

Parameter Type Required Description
elicitationId string yes The id returned when the request was created.
maxWaitSeconds number no Longest this call waits. Can only shorten the server bound (50 seconds), never extend it; minimum 1.
{ "elicitationId": "…" }
  • A bounded long-poll: waits up to min(server bound, maxWaitSeconds, time until expiry), returning the instant a decision lands.
  • If it returns "pending", the wait bound was hit before a decision — just call it again.
  • The 50-second server bound returns before the 60-second tool-call timeout most hosts use. If something between the agent and Elicitly cuts calls off sooner — some MCP gateways time out near 30 seconds — pass a maxWaitSeconds a few seconds under that limit, so the call returns "pending" instead of failing:
{ "elicitationId": "…", "maxWaitSeconds": 25 }
{ "status": "submitted" }

status is one of pending · submitted · declined · canceled · consumed · expired — see elicit_status for what each means.