whodb_confirm
Confirm and execute pending write operations after user approval. Use with a token from a previous query to finalize INSERT, UPDATE, or DELETE actions.
Instructions
Confirm and execute a pending write operation.
Best for: Executing write queries after user approval in confirm-writes mode. Not recommended for: Read queries (they execute immediately without confirmation). Common mistakes: Using an expired token (tokens expire after 5 minutes); not explaining the query to the user before confirming.
Usage Example:
{
"name": "whodb_confirm",
"arguments": {
"token": "550e8400-e29b-41d4-a716-446655440000"
}
}Workflow:
Call whodb_query with a write operation (INSERT, UPDATE, DELETE, etc.)
Receive confirmation_required=true, a confirmation_token, and confirmation_expiry
Explain to the user what the query will do in plain language
After user approves, call whodb_confirm with the token
Query executes and returns results
Token behavior: Tokens are valid for 5 minutes (expiry time is in the response). If confirmation fails due to a connection error or timeout, you can retry with the same token — it is only consumed after successful execution. Use whodb_pending to list active tokens if you lose track.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | Confirmation token from a previous whodb_query or hosted platform write response |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rows | Yes | ||
| error | No | ||
| columns | Yes | ||
| message | No | ||
| commands | No | ||
| next_steps | No | ||
| request_id | No | ||
| column_types | No | ||
| setup_status | No |