Files
genai-toolbox/docs/en/resources/tools/utility/alloydbwaitforoperation.md
prernakakkar-google 3f6ec2944e feat: Add wait for operation tool with exponential backoff (#920)
Example:

```
  alloydb-operations-get:
    kind: wait-for-operation
    source: alloydb-api-source
    method: GET
    path: /v1/projects/{{.projectId}}/locations/{{.locationId}}/operations/{{.operationId}}
    description: "Makes API call to check whether operation is done or not. This tool is run first then wait for tool. if its still in create phase trigger it after 3 minutes.  Print a message saying still not done. We will notify once its done."
    pathParams:
      - name: projectId
        type: string
        description: The dynamic path parameter
      - name: locationId
        type: string
        description: The dynamic path parameter
        default: us-central1
      - name: operationId
        type: string
        description: Operation status check for previous task

```
2025-07-24 00:04:36 +05:30

2.6 KiB

title, type, weight, description
title type weight description
alloydb-wait-for-operation docs 10 Wait for a long-running AlloyDB operation to complete.

The alloydb-wait-for-operation tool is a utility tool that waits for a long-running AlloyDB operation to complete. It does this by polling the AlloyDB Admin API operation status endpoint until the operation is finished, using exponential backoff.

{{< notice info >}} This tool is intended for developer assistant workflows with human-in-the-loop and shouldn't be used for production agents. {{< /notice >}}

Example

sources:
  alloydb-api-source:
    kind: http
    baseUrl: https://alloydb.googleapis.com
    headers:
      Authorization: Bearer ${API_KEY}
      Content-Type: application/json

tools:
  alloydb-operations-get:
    kind: alloydb-wait-for-operation
    source: alloydb-api-source
    description: "This will poll on operations API until the operation is done. For checking operation status we need projectId, locationID and operationId. Once instance is created give follow up steps on how to use the variables to bring data plane MCP server up in local and remote setup."
    delay: 1s
    maxDelay: 4m
    multiplier: 2
    maxRetries: 10

Reference

field type required description
kind string true Must be "alloydb-wait-for-operation".
source string true Name of the source the HTTP request should be sent to.
description string true A description of the tool.
delay duration false The initial delay between polling requests (e.g., 3s). Defaults to 3 seconds.
maxDelay duration false The maximum delay between polling requests (e.g., 4m). Defaults to 4 minutes.
multiplier float false The multiplier for the polling delay. The delay is multiplied by this value after each request. Defaults to 2.0.
maxRetries int false The maximum number of polling attempts before giving up. Defaults to 10.