CALL-E

Query a call run by run_id. This tool does not initiate calls or modify run state. After calling 'run_call', poll get_call_run for realtime progress updates. Poll every 1-3 seconds while activity is changing, then slow down; do not call plan_call or run_call again.

First, use this to plan the call. Always pass the user's latest message verbatim via 'user_input' (even if you also set other fields). Do not guess region/language or reformat ambiguous phone numbers. If 'ready_to_run' is false, prefer letting the user fill the missing details in the plan card UI instead of restating every question in chat. If the user answers in chat instead, call this again with 'user_input' set to the user's response. When 'ready_to_run' is true and a plan card UI is available, stop after 'plan_call' and let the plan card continue execution. Only call 'run_call' yourself if no plan card UI is available or the user explicitly asks to start or retry the call in chat. Do not guess parameters.

Executes the planned call. Use only after 'plan_call' returns 'ready_to_run=true'. Pass the 'confirm_token' exactly as received. In ChatGPT, do not call 'run_call' in the same turn if a plan card UI is available and has already started the call. Use 'run_call' there only when no plan card UI is available or the user explicitly asks to start or retry the call in chat. If the call starts, it runs asynchronously. Do not perform extra operations; the server will notify on completion. Do not call 'run_call' more than once for the same 'plan_id'. Once started, wait for the activity card updates.

Widget-only batch telemetry ingestion tool. Use this from the app UI to submit a telemetry batch for a single plan or run. Events must be sent in batches, not one-by-one.