feat: add instructions to main content area

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [go](https://go.dev/)
([source](https://redirect.github.com/golang/go)) | toolchain | patch |
`1.24.5` -> `1.24.6` |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>golang/go (go)</summary>

###
[`v1.24.6`](https://redirect.github.com/golang/go/compare/go1.24.5...go1.24.6)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/googleapis/genai-toolbox).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS41MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuNTEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

.ci/integration.cloudbuild.yaml

@@ -62,7 +62,6 @@ steps:
           postgressql \
           postgresexecutesql
 
-
   - id: "alloydb-pg"
     name: golang:1
     waitFor: ["compile-test-binary"]
@@ -121,8 +120,7 @@ steps:
       - "BIGTABLE_PROJECT=$PROJECT_ID"
       - "BIGTABLE_INSTANCE=$_BIGTABLE_INSTANCE"
       - "SERVICE_ACCOUNT_EMAIL=$SERVICE_ACCOUNT_EMAIL"
-    secretEnv:
-      ["CLIENT_ID"]
+    secretEnv: ["CLIENT_ID"]
     volumes:
       - name: "go"
         path: "/gopath"
@@ -153,7 +151,7 @@ steps:
           "BigQuery" \
           bigquery \
           bigquery
-  
+
   - id: "dataplex"
     name: golang:1
     waitFor: ["compile-test-binary"]
@@ -274,8 +272,7 @@ steps:
       - "CLOUD_SQL_MYSQL_DATABASE=$_DATABASE_NAME"
       - "CLOUD_SQL_MYSQL_REGION=$_REGION"
       - "SERVICE_ACCOUNT_EMAIL=$SERVICE_ACCOUNT_EMAIL"
-    secretEnv:
-      ["CLOUD_SQL_MYSQL_USER", "CLOUD_SQL_MYSQL_PASS", "CLIENT_ID"]
+    secretEnv: ["CLOUD_SQL_MYSQL_USER", "CLOUD_SQL_MYSQL_PASS", "CLIENT_ID"]
     volumes:
       - name: "go"
         path: "/gopath"
@@ -387,7 +384,7 @@ steps:
           sqlite
 
   - id: "couchbase"
-    name : golang:1
+    name: golang:1
     waitFor: ["compile-test-binary"]
     entrypoint: /bin/bash
     env:
@@ -395,7 +392,8 @@ steps:
       - "COUCHBASE_SCOPE=$_COUCHBASE_SCOPE"
       - "COUCHBASE_BUCKET=$_COUCHBASE_BUCKET"
       - "SERVICE_ACCOUNT_EMAIL=$SERVICE_ACCOUNT_EMAIL"
-    secretEnv: ["COUCHBASE_CONNECTION", "COUCHBASE_USER", "COUCHBASE_PASS", "CLIENT_ID"]
+    secretEnv:
+      ["COUCHBASE_CONNECTION", "COUCHBASE_USER", "COUCHBASE_PASS", "CLIENT_ID"]
     volumes:
       - name: "go"
         path: "/gopath"
@@ -408,7 +406,7 @@ steps:
           couchbase
 
   - id: "redis"
-    name : golang:1
+    name: golang:1
     waitFor: ["compile-test-binary"]
     entrypoint: /bin/bash
     env:
@@ -425,9 +423,9 @@ steps:
           "Redis" \
           redis \
           redis
-        
+
   - id: "valkey"
-    name : golang:1
+    name: golang:1
     waitFor: ["compile-test-binary"]
     entrypoint: /bin/bash
     env:
@@ -475,7 +473,13 @@ steps:
       - "FIRESTORE_PROJECT=$PROJECT_ID"
       - "SERVICE_ACCOUNT_EMAIL=$SERVICE_ACCOUNT_EMAIL"
       - "LOOKER_VERIFY_SSL=$_LOOKER_VERIFY_SSL"
-    secretEnv: ["CLIENT_ID", "LOOKER_BASE_URL", "LOOKER_CLIENT_ID", "LOOKER_CLIENT_SECRET"]
+    secretEnv:
+      [
+        "CLIENT_ID",
+        "LOOKER_BASE_URL",
+        "LOOKER_CLIENT_ID",
+        "LOOKER_CLIENT_SECRET",
+      ]
     volumes:
       - name: "go"
         path: "/gopath"
@@ -486,8 +490,6 @@ steps:
           "Looker" \
           looker \
           looker
-    
-
 
   - id: "alloydbwaitforoperation"
     name: golang:1
@@ -507,7 +509,29 @@ steps:
           "Alloydb Wait for Operation" \
           utility \
           utility/alloydbwaitforoperation
-          
+
+  - id: "tidb"
+    name: golang:1
+    waitFor: ["compile-test-binary"]
+    entrypoint: /bin/bash
+    env:
+      - "GOPATH=/gopath"
+      - "TIDB_DATABASE=$_DATABASE_NAME"
+      - "TIDB_HOST=$_TIDB_HOST"
+      - "TIDB_PORT=$_TIDB_PORT"
+      - "SERVICE_ACCOUNT_EMAIL=$SERVICE_ACCOUNT_EMAIL"
+    secretEnv: ["CLIENT_ID", "TIDB_USER", "TIDB_PASS"]
+    volumes:
+      - name: "go"
+        path: "/gopath"
+    args:
+      - -c
+      - |
+        .ci/test_with_coverage.sh \
+          "TiDB" \
+          tidb \
+          tidbsql tidbexecutesql
+
 availableSecrets:
   secretManager:
     - versionName: projects/$PROJECT_ID/secrets/cloud_sql_pg_user/versions/latest
@@ -566,7 +590,10 @@ availableSecrets:
       env: LOOKER_CLIENT_ID
     - versionName: projects/107716898620/secrets/looker_client_secret/versions/latest
       env: LOOKER_CLIENT_SECRET
-
+    - versionName: projects/107716898620/secrets/tidb_user/versions/latest
+      env: TIDB_USER
+    - versionName: projects/107716898620/secrets/tidb_pass/versions/latest
+      env: TIDB_PASS
 
 options:
   logging: CLOUD_LOGGING_ONLY
@@ -598,4 +625,6 @@ substitutions:
   _DGRAPHURL: "https://play.dgraph.io"
   _COUCHBASE_BUCKET: "couchbase-bucket"
   _COUCHBASE_SCOPE: "couchbase-scope"
-  _LOOKER_VERIFY_SSL: "true"
+  _LOOKER_VERIFY_SSL: "true"
+  _TIDB_HOST: 127.0.0.1
+  _TIDB_PORT: "4000"

.github/blunderbuss.yml

@@ -1,7 +1,7 @@
 assign_issues:
   - Yuan325
   - duwenxin99
-  - akitsch
+  - averikitsch
 assign_issues_by:
   - labels:
     - 'product: bigquery'
@@ -12,4 +12,4 @@ assign_issues_by:
 assign_prs:
   - Yuan325
   - duwenxin99
-  - akitsch
+  - averikitsch

.github/release-please.yml

@@ -24,6 +24,7 @@ extraFiles: [
     "docs/en/getting-started/local_quickstart_js.md",
     "docs/en/getting-started/local_quickstart_go.md",
     "docs/en/getting-started/mcp_quickstart/_index.md",
+    "docs/en/samples/alloydb/_index.md",
     "docs/en/samples/bigquery/local_quickstart.md",
     "docs/en/samples/bigquery/mcp_quickstart/_index.md",
     "docs/en/samples/bigquery/colab_quickstart_bigquery.ipynb",
@@ -37,6 +38,8 @@ extraFiles: [
     "docs/en/how-to/connect-ide/cloud_sql_mysql_mcp.md",
     "docs/en/how-to/connect-ide/firestore_mcp.md",
     "docs/en/how-to/connect-ide/looker_mcp.md",
+    "docs/en/how-to/connect-ide/mysql_mcp.md",
+    "docs/en/how-to/connect-ide/mssql_mcp.md",
     "docs/en/how-to/connect-ide/postgres_mcp.md",
     "docs/en/how-to/connect-ide/spanner_mcp.md",
 ]

.github/workflows/docs_deploy.yaml

@@ -55,7 +55,7 @@ jobs:
           node-version: "22"
 
       - name: Cache dependencies
-        uses: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684 # v4
+        uses: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809 # v4
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}

.github/workflows/docs_preview_deploy.yaml

@@ -67,7 +67,7 @@ jobs:
           node-version: "22"
 
       - name: Cache dependencies
-        uses: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684 # v4
+        uses: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809 # v4
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}

.github/workflows/schedule_reporter.yml

@@ -26,4 +26,4 @@ jobs:
         contents: 'read'
     uses: ./.github/workflows/cloud_build_failure_reporter.yml
     with:
-      trigger_names: "toolbox-test-nightly,toolbox-test-on-merge"
+      trigger_names: "toolbox-test-nightly,toolbox-test-on-merge,toolbox-continuous-release"

CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## [0.11.0](https://github.com/googleapis/genai-toolbox/compare/v0.11.0...v0.11.0) (2025-08-05)
+
+
+### ⚠ BREAKING CHANGES
+
+* **tools/bigquery-sql:** Ensure invoke always returns a non-null value ([#1020](https://github.com/googleapis/genai-toolbox/issues/1020)) ([9af55b6](https://github.com/googleapis/genai-toolbox/commit/9af55b651d836f268eda342ea27380e7c9967c94))
+* **tools/bigquery-execute-sql:** Update the return messages ([#1034](https://github.com/googleapis/genai-toolbox/issues/1034)) ([051e686](https://github.com/googleapis/genai-toolbox/commit/051e686476a781ca49f7617764d507916a1188b8))
+
+### Features
+
+* Add TiDB source and tool ([#829](https://github.com/googleapis/genai-toolbox/issues/829)) ([6eaf36a](https://github.com/googleapis/genai-toolbox/commit/6eaf36ac8505d523fa4f5a4ac3c97209fd688cef))
+* Interactive web UI for Toolbox  ([#1065](https://github.com/googleapis/genai-toolbox/issues/1065)) ([8749b03](https://github.com/googleapis/genai-toolbox/commit/8749b030035e65361047c4ead13dfacb8e9a9b59))
+* **prebuiltconfigs/cloud-sql-postgres:** Introduce additional parameter to limit context in list tables ([#1062](https://github.com/googleapis/genai-toolbox/issues/1062)) ([c3a58e1](https://github.com/googleapis/genai-toolbox/commit/c3a58e1d1678dc14d8de5006511df597fd75faa3))
+* **tools/looker-query-url:** Add support for `looker-query-url` tool ([#1015](https://github.com/googleapis/genai-toolbox/issues/1015)) ([327ddf0](https://github.com/googleapis/genai-toolbox/commit/327ddf0439058aa5ecd2c7ae8251fcde6aeff18c))
+* **tools/dataplex-lookup-entry:** Add support for `dataplex-lookup-entry` tool ([#1009](https://github.com/googleapis/genai-toolbox/issues/1009)) ([5fa1660](https://github.com/googleapis/genai-toolbox/commit/5fa1660fc8631989b4d13abea205b6426bb506a5))
+
+### Bug Fixes
+
+* **tools/bigquery,mssql,mysql,postgres,spanner,tidb:** Add query logging to execute-sql tools ([#1069](https://github.com/googleapis/genai-toolbox/issues/1069)) ([0527532]([https://github.com/googleapis/genai-toolbox/commit/0527532bd7085ef9eb8f9c30f430a2f2f35cef32))
+
 ## [0.10.0](https://github.com/googleapis/genai-toolbox/compare/v0.9.0...v0.10.0) (2025-07-25)
 
 

CONTRIBUTING.md

@@ -81,7 +81,7 @@ implementation](https://github.com/googleapis/genai-toolbox/blob/main/internal/s
 #### 2. Implement the New Tool
 
 We recommend looking at an [example tool
-implementation](https://github.com/googleapis/genai-toolbox/tree/main/internal/tools/postgressql).
+implementation](https://github.com/googleapis/genai-toolbox/tree/main/internal/tools/postgres/postgressql).
 
 * **Create a new directory** under `internal/tools` for your tool type (e.g.,
   `internal/tools/newdb` or `internal/tools/newdb<tool_name>`).
@@ -134,7 +134,7 @@ tools.
      5. (Optional) [RunToolInvokeWithTemplateParameters][temp-param]: tests for [template
             parameters][temp-param-doc]. Only run this test if template
             parameters apply to your tool.
-  
+
 * **Add the new database to the test config** in
   [integration.cloudbuild.yaml](.ci/integration.cloudbuild.yaml).
 

README.md

@@ -114,7 +114,7 @@ To install Toolbox as a binary:
 <!-- {x-release-please-start-version} -->
 ```sh
 # see releases page for other versions
-export VERSION=0.10.0
+export VERSION=0.11.0
 curl -O https://storage.googleapis.com/genai-toolbox/v$VERSION/linux/amd64/toolbox
 chmod +x toolbox
 ```
@@ -127,12 +127,23 @@ You can also install Toolbox as a container:
 
 ```sh
 # see releases page for other versions
-export VERSION=0.10.0
+export VERSION=0.11.0
 docker pull us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:$VERSION
 ```
 
 </details>
 
+<details>
+<summary>Homebrew</summary>
+
+To install Toolbox using Homebrew on macOS or Linux:
+
+```sh
+brew install mcp-toolbox
+```
+
+</details>
+
 <details>
 <summary>Compile from source</summary>
 
@@ -140,7 +151,7 @@ To install from source, ensure you have the latest version of
 [Go installed](https://go.dev/doc/install), and then run the following command:
 
 ```sh
-go install github.com/googleapis/genai-toolbox@v0.10.0
+go install github.com/googleapis/genai-toolbox@v0.11.0
 ```
 <!-- {x-release-please-end} -->
 
@@ -154,8 +165,18 @@ execute `toolbox` to start the server:
 ```sh
 ./toolbox --tools-file "tools.yaml"
 ```
+
 > [!NOTE]
-> Toolbox enables dynamic reloading by default. To disable, use the `--disable-reload` flag.
+> Toolbox enables dynamic reloading by default. To disable, use the
+> `--disable-reload` flag.
+
+#### Homebrew Users
+
+If you installed Toolbox using Homebrew, the `toolbox` binary is available in your system path. You can start the server with the same command:
+
+```sh
+toolbox --tools-file "tools.yaml"
+```
 
 You can use `toolbox help` for a full list of flags! To stop the server, send a
 terminate signal (`ctrl+c` on most platforms).
@@ -509,9 +530,9 @@ For more detailed instructions on using the Toolbox Core SDK, see the
       // Convert the tool using the tbgenkit package
       // Use this tool with Genkit Go
       genkitTool, err := tbgenkit.ToGenkitTool(tool, g)
-  		if err != nil {
-  			log.Fatalf("Failed to convert tool: %v\n", err)
-  		}
+      if err != nil {
+        log.Fatalf("Failed to convert tool: %v\n", err)
+      }
     }
     ```
 

cmd/BUILD

@@ -1,20 +0,0 @@
-load("//tools/build_defs/go:go_library.bzl", "go_library")
-load("//tools/build_defs/go:go_test.bzl", "go_test")
-
-go_library(
-    name = "cmd",
-    srcs = [
-        "options.go",
-        "root.go",
-    ],
-    embedsrcs = ["version.txt"],
-)
-
-go_test(
-    name = "cmd_test",
-    srcs = [
-        "options_test.go",
-        "root_test.go",
-    ],
-    library = ":cmd",
-)

cmd/root.go

@@ -51,6 +51,7 @@ import (
 	_ "github.com/googleapis/genai-toolbox/internal/tools/bigquery/bigquerysql"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/bigtable"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/couchbase"
+	_ "github.com/googleapis/genai-toolbox/internal/tools/dataplex/dataplexlookupentry"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/dataplex/dataplexsearchentries"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/dgraph"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestoredeletedocuments"
@@ -67,8 +68,10 @@ import (
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookergetmeasures"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookergetmodels"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookergetparameters"
+	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookermakelook"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookerquery"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookerquerysql"
+	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookerqueryurl"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookerrunlook"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/mongodb/mongodbaggregate"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/mongodb/mongodbdeletemany"
@@ -92,6 +95,8 @@ import (
 	_ "github.com/googleapis/genai-toolbox/internal/tools/spanner/spannerexecutesql"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/spanner/spannersql"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/sqlitesql"
+	_ "github.com/googleapis/genai-toolbox/internal/tools/tidb/tidbexecutesql"
+	_ "github.com/googleapis/genai-toolbox/internal/tools/tidb/tidbsql"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/utility/alloydbwaitforoperation"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/utility/wait"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/valkey"
@@ -118,6 +123,7 @@ import (
 	_ "github.com/googleapis/genai-toolbox/internal/sources/redis"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/spanner"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/sqlite"
+	_ "github.com/googleapis/genai-toolbox/internal/sources/tidb"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/valkey"
 )
 
@@ -216,9 +222,10 @@ func NewCommand(opts ...Option) *Command {
 	flags.BoolVar(&cmd.cfg.TelemetryGCP, "telemetry-gcp", false, "Enable exporting directly to Google Cloud Monitoring.")
 	flags.StringVar(&cmd.cfg.TelemetryOTLP, "telemetry-otlp", "", "Enable exporting using OpenTelemetry Protocol (OTLP) to the specified endpoint (e.g. 'http://127.0.0.1:4318')")
 	flags.StringVar(&cmd.cfg.TelemetryServiceName, "telemetry-service-name", "toolbox", "Sets the value of the service.name resource attribute for telemetry data.")
-	flags.StringVar(&cmd.prebuiltConfig, "prebuilt", "", "Use a prebuilt tool configuration by source type. Cannot be used with --tools-file. Allowed: 'alloydb-postgres-admin', alloydb-postgres', 'bigquery', 'cloud-sql-mysql', 'cloud-sql-postgres', 'cloud-sql-mssql', 'dataplex', 'firestore', 'mssql', 'mysql', 'postgres', 'spanner', 'spanner-postgres'.")
+	flags.StringVar(&cmd.prebuiltConfig, "prebuilt", "", "Use a prebuilt tool configuration by source type. Cannot be used with --tools-file. Allowed: 'alloydb-postgres-admin', alloydb-postgres', 'bigquery', 'cloud-sql-mysql', 'cloud-sql-postgres', 'cloud-sql-mssql', 'dataplex', 'firestore', 'looker', 'mssql', 'mysql', 'postgres', 'spanner', 'spanner-postgres'.")
 	flags.BoolVar(&cmd.cfg.Stdio, "stdio", false, "Listens via MCP STDIO instead of acting as a remote HTTP server.")
 	flags.BoolVar(&cmd.cfg.DisableReload, "disable-reload", false, "Disables dynamic reloading of tools file.")
+	flags.BoolVar(&cmd.cfg.UI, "ui", false, "Launches the Toolbox UI web server.")
 
 	// wrap RunE command so that we have access to original Command object
 	cmd.RunE = func(*cobra.Command, []string) error { return run(cmd) }
@@ -795,6 +802,9 @@ func run(cmd *Command) error {
 			return errMsg
 		}
 		cmd.logger.InfoContext(ctx, "Server ready to serve!")
+		if cmd.cfg.UI {
+			cmd.logger.InfoContext(ctx, "Toolbox UI is up and running at: http://localhost:5000/ui")
+		}
 
 		go func() {
 			defer close(srvErr)

cmd/root_test.go

@@ -1250,7 +1250,7 @@ func TestPrebuiltTools(t *testing.T) {
 			wantToolset: server.ToolsetConfigs{
 				"dataplex-tools": tools.ToolsetConfig{
 					Name:      "dataplex-tools",
-					ToolNames: []string{"dataplex_search_entries"},
+					ToolNames: []string{"dataplex_search_entries", "dataplex_lookup_entry"},
 				},
 			},
 		},
@@ -1290,7 +1290,7 @@ func TestPrebuiltTools(t *testing.T) {
 			wantToolset: server.ToolsetConfigs{
 				"looker-tools": tools.ToolsetConfig{
 					Name:      "looker-tools",
-					ToolNames: []string{"get_models", "get_explores", "get_dimensions", "get_measures", "get_filters", "get_parameters", "query", "query_sql", "get_looks", "run_look"},
+					ToolNames: []string{"get_models", "get_explores", "get_dimensions", "get_measures", "get_filters", "get_parameters", "query", "query_sql", "query_url", "get_looks", "run_look", "make_look"},
 				},
 			},
 		},

cmd/version.txt

@@ -1 +1 @@
-0.10.0
+0.11.0

docs/en/_index.md

@@ -4,12 +4,12 @@ type: docs
 notoc: false
 weight: 1
 description: >
-  All of Toolbox's documentation. 
+  All of Toolbox's documentation.
 ---
 
 <html>
   <head>
     <link rel="canonical" href="getting-started/introduction/"/>
-    <meta http-equiv="refresh" content="0;url=getting-started/introduction"/>
+    <meta http-equiv="refresh" content="0;url=getting-started/introduction/"/>
   </head>
 </html>

docs/en/concepts/telemetry/index.md

@@ -3,7 +3,7 @@ title: "Telemetry"
 type: docs
 weight: 2
 description: >
-  An overview of telemetry and observability in Toolbox. 
+  An overview of telemetry and observability in Toolbox.
 ---
 
 ## About
@@ -158,7 +158,7 @@ enabled:
 
 - [Cloud Logging API](https://cloud.google.com/logging/docs/api/enable-api)
 - [Cloud Monitoring API](https://cloud.google.com/monitoring/api/enable-api)
-- [Cloud Trace API](https://cloud.google.com/apis/enableflow?apiid=cloudtrace.googleapis.com)
+- [Cloud Trace API](https://console.cloud.google.com/apis/enableflow?apiid=cloudtrace.googleapis.com)
 {{< /notice >}}
 
 #### OTLP Exporter
@@ -177,7 +177,7 @@ It receives telemetry data, transforms it, and then exports data to backends
 that can store it permanently. Toolbox provide an option to export telemetry
 data to user's choice of backend(s) that are compatible with the Open Telemetry
 Protocol (OTLP). If you would like to use a collector, please refer to this
-[Export Telemetry using the Otel Collector](../how-to/export_telemetry.md).
+[Export Telemetry using the Otel Collector](../../how-to/export_telemetry.md).
 
 ### Flags
 

docs/en/getting-started/colab_quickstart.ipynb

@@ -234,7 +234,7 @@
       },
       "outputs": [],
       "source": [
-        "version = \"0.10.0\" # x-release-please-version\n",
+        "version = \"0.11.0\" # x-release-please-version\n",
         "! curl -O https://storage.googleapis.com/genai-toolbox/v{version}/linux/amd64/toolbox\n",
         "\n",
         "# Make the binary executable\n",

docs/en/getting-started/introduction/_index.md

@@ -86,7 +86,7 @@ To install Toolbox as a binary:
 
 ```sh
 # see releases page for other versions
-export VERSION=0.10.0
+export VERSION=0.11.0
 curl -O https://storage.googleapis.com/genai-toolbox/v$VERSION/linux/amd64/toolbox
 chmod +x toolbox
 ```
@@ -97,10 +97,17 @@ You can also install Toolbox as a container:
 
 ```sh
 # see releases page for other versions
-export VERSION=0.10.0
+export VERSION=0.11.0
 docker pull us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:$VERSION
 ```
 
+{{% /tab %}}
+{{% tab header="Homebrew" lang="en" %}}
+To install Toolbox using Homebrew on macOS or Linux:
+
+```sh
+brew install mcp-toolbox
+```
 {{% /tab %}}
 {{% tab header="Compile from source" lang="en" %}}
 
@@ -108,7 +115,7 @@ To install from source, ensure you have the latest version of
 [Go installed](https://go.dev/doc/install), and then run the following command:
 
 ```sh
-go install github.com/googleapis/genai-toolbox@v0.10.0
+go install github.com/googleapis/genai-toolbox@v0.11.0
 ```
 
 {{% /tab %}}
@@ -123,15 +130,34 @@ execute `toolbox` to start the server:
 ```sh
 ./toolbox --tools-file "tools.yaml"
 ```
+
 {{< notice note >}}
-Toolbox enables dynamic reloading by default. To disable, use the `--disable-reload` flag.
+Toolbox enables dynamic reloading by default. To disable, use the
+`--disable-reload` flag.
 {{< /notice >}}
 
+#### Launching Toolbox UI
+
+To launch Toolbox's interactive UI, use the `--ui` flag. This allows you to test tools and toolsets
+with features such as authorized parameters. To learn more, visit [Toolbox UI](../../how-to/use-toolbox-ui/index.md).
+
+```sh
+./toolbox --ui
+```
+
+#### Homebrew Users
+
+If you installed Toolbox using Homebrew, the `toolbox` binary is available in your system path. You can start the server with the same command:
+
+```sh
+toolbox --tools-file "tools.yaml"
+```
+
 You can use `toolbox help` for a full list of flags! To stop the server, send a
 terminate signal (`ctrl+c` on most platforms).
 
 For more detailed documentation on deploying to different environments, check
-out the resources in the [How-to section](../../how-to/_index.md)
+out the resources in the [How-to section](../../how-to/)
 
 ### Integrating your application
 
@@ -139,6 +165,7 @@ Once your server is up and running, you can load the tools into your
 application. See below the list of Client SDKs for using various frameworks:
 
 #### Python
+
 {{< tabpane text=true persist=header >}}
 {{% tab header="Core" lang="en" %}}
 
@@ -151,7 +178,7 @@ from toolbox_core import ToolboxClient
 
 # update the url to point to your server
 
-async with ToolboxClient("<http://127.0.0.1:5000>") as client:
+async with ToolboxClient("http://127.0.0.1:5000") as client:
 
     # these tools can be passed to your application!
     tools = await client.load_toolset("toolset_name")
@@ -172,7 +199,7 @@ from toolbox_langchain import ToolboxClient
 
 # update the url to point to your server
 
-async with ToolboxClient("<http://127.0.0.1:5000>") as client:
+async with ToolboxClient("http://127.0.0.1:5000") as client:
 
     # these tools can be passed to your application!
     tools = client.load_toolset()
@@ -193,7 +220,7 @@ from toolbox_llamaindex import ToolboxClient
 
 # update the url to point to your server
 
-async with ToolboxClient("<http://127.0.0.1:5000>") as client:
+async with ToolboxClient("http://127.0.0.1:5000") as client:
 
 # these tools can be passed to your application
 
@@ -303,7 +330,7 @@ const toolboxTools = await client.loadToolset('toolsetName');
 const getTool = (toolboxTool) => tool({
     name: toolboxTool.getName(),
     description: toolboxTool.getDescription(),
-    parameters: toolboxTool.getParams(),
+    parameters: toolboxTool.getParamSchema(),
     execute: toolboxTool
 });;
 
@@ -565,4 +592,6 @@ func main() {
 For more detailed instructions on using the Toolbox Go SDK, see the
 [project's README](https://github.com/googleapis/mcp-toolbox-sdk-go/blob/main/core/README.md).
 
-For end-to-end samples on using the Toolbox Go SDK with orchestration frameworks, see the [project's samples](https://github.com/googleapis/mcp-toolbox-sdk-go/tree/main/core/samples)
+For end-to-end samples on using the Toolbox Go SDK with orchestration
+frameworks, see the [project's
+samples](https://github.com/googleapis/mcp-toolbox-sdk-go/tree/main/core/samples)

docs/en/getting-started/local_quickstart.md

@@ -19,7 +19,9 @@ This guide assumes you have already done the following:
 
 ### Cloud Setup (Optional)
 
-If you plan to use **Google Cloud’s Vertex AI** with your agent (e.g., using `vertexai=True` or a Google GenAI model), follow these one-time setup steps for local development:
+If you plan to use **Google Cloud’s Vertex AI** with your agent (e.g., using
+`vertexai=True` or a Google GenAI model), follow these one-time setup steps for
+local development:
 
 1. [Install the Google Cloud CLI](https://cloud.google.com/sdk/docs/install)
 1. [Set up Application Default Credentials (ADC)](https://cloud.google.com/docs/authentication/set-up-adc-local-dev-environment)
@@ -135,7 +137,7 @@ postgres` and a password next time.
 
     ```sql
     INSERT INTO hotels(id, name, location, price_tier, checkin_date, checkout_date, booked)
-    VALUES 
+    VALUES
       (1, 'Hilton Basel', 'Basel', 'Luxury', '2024-04-22', '2024-04-20', B'0'),
       (2, 'Marriott Zurich', 'Zurich', 'Upscale', '2024-04-14', '2024-04-21', B'0'),
       (3, 'Hyatt Regency Basel', 'Basel', 'Upper Upscale', '2024-04-02', '2024-04-20', B'0'),
@@ -154,7 +156,6 @@ postgres` and a password next time.
     \q
     ```
 
-
 ## Step 2: Install and configure Toolbox
 
 In this section, we will download Toolbox, configure our tools in a
@@ -170,7 +171,7 @@ In this section, we will download Toolbox, configure our tools in a
     <!-- {x-release-please-start-version} -->
     ```bash
     export OS="linux/amd64" # one of linux/amd64, darwin/arm64, darwin/amd64, or windows/amd64
-    curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/$OS/toolbox
+    curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/$OS/toolbox
     ```
     <!-- {x-release-please-end} -->
 
@@ -271,8 +272,10 @@ In this section, we will download Toolbox, configure our tools in a
     ```bash
     ./toolbox --tools-file "tools.yaml"
     ```
+
     {{< notice note >}}
-    Toolbox enables dynamic reloading by default. To disable, use the `--disable-reload` flag.
+    Toolbox enables dynamic reloading by default. To disable, use the
+    `--disable-reload` flag.
     {{< /notice >}}
 
 ## Step 3: Connect your agent to Toolbox

docs/en/getting-started/local_quickstart_go.md

@@ -15,7 +15,8 @@ This guide assumes you have already done the following:
 
 ### Cloud Setup (Optional)
 
-If you plan to use **Google Cloud’s Vertex AI** with your agent (e.g., using Gemini or PaLM models), follow these one-time setup steps:
+If you plan to use **Google Cloud’s Vertex AI** with your agent (e.g., using
+Gemini or PaLM models), follow these one-time setup steps:
 
 1. [Install the Google Cloud CLI]
 1. [Set up Application Default Credentials (ADC)]
@@ -29,8 +30,8 @@ If you plan to use **Google Cloud’s Vertex AI** with your agent (e.g., using G
 [Go (v1.24.2 or higher)]: https://go.dev/doc/install
 [install-postgres]: https://www.postgresql.org/download/
 [Install the Google Cloud CLI]: https://cloud.google.com/sdk/docs/install
-[Set up Application Default Credentials (ADC)]: https://cloud.google.com/docs/authentication/set-up-adc-local-dev-environment
-
+[Set up Application Default Credentials (ADC)]:
+    https://cloud.google.com/docs/authentication/set-up-adc-local-dev-environment
 
 ## Step 1: Set up your database
 
@@ -166,7 +167,7 @@ In this section, we will download Toolbox, configure our tools in a
     <!-- {x-release-please-start-version} -->
     ```bash
     export OS="linux/amd64" # one of linux/amd64, darwin/arm64, darwin/amd64, or windows/amd64
-    curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/$OS/toolbox
+    curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/$OS/toolbox
     ```
     <!-- {x-release-please-end} -->
 
@@ -267,8 +268,10 @@ In this section, we will download Toolbox, configure our tools in a
     ```bash
     ./toolbox --tools-file "tools.yaml"
     ```
+
   {{< notice note >}}
-    Toolbox enables dynamic reloading by default. To disable, use the `--disable-reload` flag.
+    Toolbox enables dynamic reloading by default. To disable, use the
+    `--disable-reload` flag.
   {{< /notice >}}
 
 ## Step 3: Connect your agent to Toolbox
@@ -282,13 +285,15 @@ from Toolbox.
     go mod init main
     ```
 
-1. In a new terminal, install the [SDK](https://pkg.go.dev/github.com/googleapis/mcp-toolbox-sdk-go).
+1. In a new terminal, install the
+   [SDK](https://pkg.go.dev/github.com/googleapis/mcp-toolbox-sdk-go).
 
     ```bash
     go get github.com/googleapis/mcp-toolbox-sdk-go
     ```
 
-1. Create a new file named `hotelagent.go` and copy the following code to create an agent:
+1. Create a new file named `hotelagent.go` and copy the following code to create
+   an agent:
 
     {{< tabpane persist=header >}}
 {{< tab header="LangChain Go" lang="go" >}}
@@ -917,5 +922,6 @@ func main() {
     ```
 
 {{< notice info >}}
-For more information, visit the [Go SDK repo](https://github.com/googleapis/mcp-toolbox-sdk-go).
-{{</ notice >}}
+For more information, visit the [Go SDK
+repo](https://github.com/googleapis/mcp-toolbox-sdk-go).
+{{</ notice >}}

docs/en/getting-started/local_quickstart_js.md

@@ -15,7 +15,8 @@ This guide assumes you have already done the following:
 
 ### Cloud Setup (Optional)
 
-If you plan to use **Google Cloud’s Vertex AI** with your agent (e.g., using Gemini or PaLM models), follow these one-time setup steps:
+If you plan to use **Google Cloud’s Vertex AI** with your agent (e.g., using
+Gemini or PaLM models), follow these one-time setup steps:
 
 1. [Install the Google Cloud CLI]
 1. [Set up Application Default Credentials (ADC)]
@@ -29,8 +30,8 @@ If you plan to use **Google Cloud’s Vertex AI** with your agent (e.g., using G
 [Node.js (v18 or higher)]: https://nodejs.org/
 [install-postgres]: https://www.postgresql.org/download/
 [Install the Google Cloud CLI]: https://cloud.google.com/sdk/docs/install
-[Set up Application Default Credentials (ADC)]: https://cloud.google.com/docs/authentication/set-up-adc-local-dev-environment
-
+[Set up Application Default Credentials (ADC)]:
+    https://cloud.google.com/docs/authentication/set-up-adc-local-dev-environment
 
 ## Step 1: Set up your database
 
@@ -132,7 +133,7 @@ postgres` and a password next time.
 
     ```sql
     INSERT INTO hotels(id, name, location, price_tier, checkin_date, checkout_date, booked)
-    VALUES 
+    VALUES
       (1, 'Hilton Basel', 'Basel', 'Luxury', '2024-04-22', '2024-04-20', B'0'),
       (2, 'Marriott Zurich', 'Zurich', 'Upscale', '2024-04-14', '2024-04-21', B'0'),
       (3, 'Hyatt Regency Basel', 'Basel', 'Upper Upscale', '2024-04-02', '2024-04-20', B'0'),
@@ -166,7 +167,7 @@ In this section, we will download Toolbox, configure our tools in a
     <!-- {x-release-please-start-version} -->
     ```bash
     export OS="linux/amd64" # one of linux/amd64, darwin/arm64, darwin/amd64, or windows/amd64
-    curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/$OS/toolbox
+    curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/$OS/toolbox
     ```
     <!-- {x-release-please-end} -->
 
@@ -267,6 +268,7 @@ In this section, we will download Toolbox, configure our tools in a
     ```bash
     ./toolbox --tools-file "tools.yaml"
     ```
+
   {{< notice note >}}
     Toolbox enables dynamic reloading by default. To disable, use the `--disable-reload` flag.
   {{< /notice >}}
@@ -292,7 +294,7 @@ from Toolbox.
 
    {{< tabpane persist=header >}}
 {{< tab header="LangChain" lang="bash" >}}
-npm install langchain @langchain/google-vertexai
+npm install langchain @langchain/google-genai
 {{< /tab >}}
 {{< tab header="GenkitJS" lang="bash" >}}
 npm install genkit @genkit-ai/vertexai
@@ -307,7 +309,7 @@ npm install llamaindex @llamaindex/google @llamaindex/workflow
     {{< tabpane persist=header >}}
 {{< tab header="LangChain" lang="js" >}}
 
-import { ChatVertexAI } from "@langchain/google-vertexai";
+import { ChatGoogleGenerativeAI } from "@langchain/google-genai";
 import { ToolboxClient } from "@toolbox-sdk/core";
 import { tool } from "@langchain/core/tools";
 import { createReactAgent } from "@langchain/langgraph/prebuilt";
@@ -334,11 +336,10 @@ const queries = [
 ];
 
 async function runApplication() {
-  const model = new ChatVertexAI({
+  const model = new ChatGoogleGenerativeAI({
     model: "gemini-2.0-flash",
   });
 
-
   const client = new ToolboxClient("http://127.0.0.1:5000");
   const toolboxTools = await client.loadToolset("my-toolset");
 
@@ -363,7 +364,6 @@ async function runApplication() {
     },
   };
 
-
   for (const query of queries) {
     const agentOutput = await agent.invoke(
     {
@@ -466,14 +466,14 @@ async function run() {
           }
         })
       );
-      
+
       conversationHistory.push(...toolResponses);
-      
+
       // Call the AI again with the tool results.
       response = await ai.generate({ messages: conversationHistory, tools });
       conversationHistory.push(response.message);
     }
-    
+
     console.log(response.text);
   }
 }
@@ -575,4 +575,4 @@ main();
 
 {{< notice info >}}
 For more information, visit the [JS SDK repo](https://github.com/googleapis/mcp-toolbox-sdk-js).
-{{</ notice >}}
+{{</ notice >}}

docs/en/getting-started/mcp_quickstart/_index.md

@@ -71,7 +71,7 @@ access by our agent, and create a database user for Toolbox to connect with.
 
     ```sql
     INSERT INTO hotels(id, name, location, price_tier, checkin_date, checkout_date, booked)
-    VALUES 
+    VALUES
       (1, 'Hilton Basel', 'Basel', 'Luxury', '2024-04-22', '2024-04-20', B'0'),
       (2, 'Marriott Zurich', 'Zurich', 'Upscale', '2024-04-14', '2024-04-21', B'0'),
       (3, 'Hyatt Regency Basel', 'Basel', 'Upper Upscale', '2024-04-02', '2024-04-20', B'0'),
@@ -105,7 +105,7 @@ In this section, we will download Toolbox, configure our tools in a
     <!-- {x-release-please-start-version} -->
     ```bash
     export OS="linux/amd64" # one of linux/amd64, darwin/arm64, darwin/amd64, or windows/amd64
-    curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/$OS/toolbox
+    curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/$OS/toolbox
     ```
     <!-- {x-release-please-end} -->
 
@@ -200,7 +200,7 @@ In this section, we will download Toolbox, configure our tools in a
     ```
 
     For more info on tools, check out the
-    [Tools](../../resources/tools/_index.md) section.
+    [Tools](../../resources/tools/) section.
 
 1. Run the Toolbox server, pointing to the `tools.yaml` file created earlier:
 
@@ -218,7 +218,8 @@ In this section, we will download Toolbox, configure our tools in a
 
 1. Type `y` when it asks to install the inspector package.
 
-1. It should show the following when the MCP Inspector is up and running (please take note of `<YOUR_SESSION_TOKEN>`):
+1. It should show the following when the MCP Inspector is up and running (please
+   take note of `<YOUR_SESSION_TOKEN>`):
 
     ```bash
     Starting MCP inspector...
@@ -236,7 +237,8 @@ In this section, we will download Toolbox, configure our tools in a
 
 1. For `URL`, type in `http://127.0.0.1:5000/mcp`.
 
-1. For `Configuration` -> `Proxy Session Token`, make sure `<YOUR_SESSION_TOKEN>` is present.
+1. For `Configuration` -> `Proxy Session Token`, make sure
+   `<YOUR_SESSION_TOKEN>` is present.
 
 1. Click Connect.
 
@@ -246,4 +248,4 @@ In this section, we will download Toolbox, configure our tools in a
 
     ![inspector_tools](./inspector_tools.png)
 
-1. Test out your tools here!
+1. Test out your tools here!

docs/en/how-to/connect-ide/alloydb_pg_admin_mcp.md

@@ -6,299 +6,9 @@ description: >
   Create your AlloyDB database with MCP Toolbox.
 ---
 
-This guide covers how to use [MCP Toolbox for Databases][toolbox] to create AlloyDB clusters and instances from IDE enabling their E2E journey.
-
-- [Cursor][cursor]
-- [Windsurf][windsurf] (Codium)
-- [Visual Studio Code ][vscode] (Copilot)
-- [Cline][cline] (VS Code extension)
-- [Claude desktop][claudedesktop]
-- [Claude code][claudecode]
-- [Gemini CLI][geminicli]
-- [Gemini Code Assist][geminicodeassist]
-
-[toolbox]: https://github.com/googleapis/genai-toolbox
-[cursor]: #configure-your-mcp-client
-[windsurf]: #configure-your-mcp-client
-[vscode]: #configure-your-mcp-client
-[cline]: #configure-your-mcp-client
-[claudedesktop]: #configure-your-mcp-client
-[claudecode]: #configure-your-mcp-client
-[geminicli]: #configure-your-mcp-client
-[geminicodeassist]: #configure-your-mcp-client
-
-## Before you begin
-
-1. In the Google Cloud console, on the [project selector page](https://console.cloud.google.com/projectselector2/home/dashboard), select or create a Google Cloud project.
-
-1. [Make sure that billing is enabled for your Google Cloud project](https://cloud.google.com/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).
-
-## Install MCP Toolbox
-
-1. Download the latest version of Toolbox as a binary. Select the [correct binary](https://github.com/googleapis/genai-toolbox/releases) corresponding to your OS and CPU architecture. You are required to use Toolbox version V0.10.0+:
-
-   <!-- {x-release-please-start-version} -->
-   {{< tabpane persist=header >}}
-{{< tab header="linux/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/linux/amd64/toolbox
-{{< /tab >}}
-
-{{< tab header="darwin/arm64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/darwin/arm64/toolbox
-{{< /tab >}}
-
-{{< tab header="darwin/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/darwin/amd64/toolbox
-{{< /tab >}}
-
-{{< tab header="windows/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/windows/amd64/toolbox.exe
-{{< /tab >}}
-{{< /tabpane >}}
-    <!-- {x-release-please-end} -->
-
-1. Make the binary executable:
-
-   ```bash
-   chmod +x toolbox
-   ```
-
-1. Verify the installation:
-
-   ```bash
-   ./toolbox --version
-   ```
-
-## Configure your MCP Client
-
-{{< tabpane text=true >}}
-{{% tab header="Claude code" lang="en" %}}
-
-1. Install [Claude Code](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview).
-1. Create a `.mcp.json` file in your project root if it doesn't exist.
-1. Generate Access token to be used as API_KEY using `gcloud auth print-access-token`.
-
-> **Note:** The lifetime of token is 1 hour.
-
-1. Add the following configuration, replace the environment variables with your values, and save:
-
-   ```json
-   {
-     "mcpServers": {
-       "alloydb-admin": {
-         "command": "./PATH/TO/toolbox",
-         "args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
-         "env": {
-           "API_KEY": "your-api-key"
-         }
-       }
-     }
-   }
-   ```
-
-1. Restart Claude code to apply the new configuration.
-   {{% /tab %}}
-
-{{% tab header="Claude desktop" lang="en" %}}
-
-1. Open [Claude desktop](https://claude.ai/download) and navigate to Settings.
-1. Under the Developer tab, tap Edit Config to open the configuration file.
-1. Generate Access token to be used as API_KEY using `gcloud auth print-access-token`.
-
-> **Note:** The lifetime of token is 1 hour.
-
-1. Add the following configuration, replace the environment variables with your values, and save:
-
-   ```json
-   {
-     "mcpServers": {
-       "alloydb-admin": {
-         "command": "./PATH/TO/toolbox",
-         "args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
-         "env": {
-           "API_KEY": "your-api-key"
-         }
-       }
-     }
-   }
-   ```
-
-1. Restart Claude desktop.
-1. From the new chat screen, you should see a hammer (MCP) icon appear with the new MCP server available.
-   {{% /tab %}}
-
-{{% tab header="Cline" lang="en" %}}
-
-1. Open the [Cline](https://github.com/cline/cline) extension in VS Code and tap the **MCP Servers** icon.
-1. Tap Configure MCP Servers to open the configuration file.
-1. Generate Access token to be used as API_KEY using `gcloud auth print-access-token`.
-
-> **Note:** The lifetime of token is 1 hour.
-
-1. Add the following configuration, replace the environment variables with your values, and save:
-
-   ```json
-   {
-     "mcpServers": {
-       "alloydb-admin": {
-         "command": "./PATH/TO/toolbox",
-         "args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
-         "env": {
-           "API_KEY": "your-api-key"
-         }
-       }
-     }
-   }
-   ```
-
-1. You should see a green active status after the server is successfully connected.
-   {{% /tab %}}
-
-{{% tab header="Cursor" lang="en" %}}
-
-1. Create a `.cursor` directory in your project root if it doesn't exist.
-1. Create a `.cursor/mcp.json` file if it doesn't exist and open it.
-1. Generate Access token to be used as API_KEY using `gcloud auth print-access-token`.
-
-> **Note:** The lifetime of token is 1 hour.
-
-1. Add the following configuration, replace the environment variables with your values, and save:
-
-   ```json
-   {
-     "mcpServers": {
-       "alloydb-admin": {
-         "command": "./PATH/TO/toolbox",
-         "args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
-         "env": {
-           "API_KEY": "your-api-key"
-         }
-       }
-     }
-   }
-   ```
-
-1. [Cursor](https://www.cursor.com/) and navigate to **Settings > Cursor Settings > MCP**. You should see a green active status after the server is successfully connected.
-   {{% /tab %}}
-
-{{% tab header="Visual Studio Code (Copilot)" lang="en" %}}
-
-1.  Open [VS Code](https://code.visualstudio.com/docs/copilot/overview) and create a `.vscode` directory in your project root if it doesn't exist.
-1.  Create a `.vscode/mcp.json` file if it doesn't exist and open it.
-1.  Generate Access token to be used as API_KEY using `gcloud auth print-access-token`.
-
-> **Note:** The lifetime of token is 1 hour.
-
-1.  Add the following configuration, replace the environment variables with your values, and save:
-
-```json
-{
-  "mcpServers": {
-    "alloydb-admin": {
-      "command": "./PATH/TO/toolbox",
-      "args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
-      "env": {
-        "API_KEY": "your-api-key"
-      }
-    }
-  }
-}
-```
-
-{{% /tab %}}
-
-{{% tab header="Windsurf" lang="en" %}}
-
-1.  Open [Windsurf](https://docs.codeium.com/windsurf) and navigate to the Cascade assistant.
-1.  Tap on the hammer (MCP) icon, then Configure to open the configuration file.
-1.  Generate Access token to be used as API_KEY using `gcloud auth print-access-token`.
-
-> **Note:** The lifetime of token is 1 hour.
-
-1.  Add the following configuration, replace the environment variables with your values, and save:
-
-```json
-{
-  "mcpServers": {
-    "alloydb-admin": {
-      "command": "./PATH/TO/toolbox",
-      "args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
-      "env": {
-        "API_KEY": "your-api-key"
-      }
-    }
-  }
-}
-```
-
-{{% /tab %}}
-{{% tab header="Gemini CLI" lang="en" %}}
-
-1.  Install the [Gemini CLI](https://github.com/google-gemini/gemini-cli?tab=readme-ov-file#quickstart).
-1.  In your working directory, create a folder named `.gemini`. Within it, create a `settings.json` file.
-1.  Generate Access token to be used as API_KEY using `gcloud auth print-access-token`.
-
-> **Note:** The lifetime of token is 1 hour.
-
-1.  Add the following configuration, replace the environment variables with your values, and save:
-
-```json
-{
-  "mcpServers": {
-    "alloydb-admin": {
-      "command": "./PATH/TO/toolbox",
-      "args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
-      "env": {
-        "API_KEY": "your-api-key"
-      }
-    }
-  }
-}
-```
-
-{{% /tab %}}
-{{% tab header="Gemini Code Assist" lang="en" %}}
-
-1.  Install the [Gemini Code Assist](https://marketplace.visualstudio.com/items?itemName=Google.geminicodeassist) extension in Visual Studio Code.
-1.  Enable Agent Mode in Gemini Code Assist chat.
-1.  In your working directory, create a folder named `.gemini`. Within it, create a `settings.json` file.
-1.  Generate Access token to be used as API_KEY using `gcloud auth print-access-token`.
-
-> **Note:** The lifetime of token is 1 hour.
-
-1.  Add the following configuration, replace the environment variables with your values, and save:
-
-```json
-{
-  "mcpServers": {
-    "alloydb-admin": {
-      "command": "./PATH/TO/toolbox",
-      "args": ["--prebuilt", "alloydb-postgres-admin", "--stdio"],
-      "env": {
-        "API_KEY": "your-api-key"
-      }
-    }
-  }
-}
-```
-
-{{% /tab %}}
-{{< /tabpane >}}
-
-## Use Tools
-
-Your AI tool is now connected to AlloyDB using MCP. Try asking your AI assistant to create a database, cluster or instance.
-
-The following tools are available to the LLM:
-
-1. **alloydb-create-cluster**: creates alloydb cluster
-1. **alloydb-create-instance**: creates alloydb instance (PRIMARY, READ_POOL or SECONDARY)
-1. **alloydb-get-operation**: polls on operations API until the operation is done.
-
-{{< notice note >}}
-Prebuilt tools are pre-1.0, so expect some tool changes between versions. LLMs will adapt to the tools available, so this shouldn't affect most users.
-{{< /notice >}}
-
-## Connect to your Data
-
-After setting up an AlloyDB cluster and instance, you can [connect your IDE to the database](https://cloud.google.com/alloydb/docs/pre-built-tools-with-mcp-toolbox).
+<html>
+  <head>
+    <link rel="canonical" href="https://cloud.google.com/alloydb/docs/create-database-with-mcp-toolbox"/>
+    <meta http-equiv="refresh" content="0;url=https://cloud.google.com/alloydb/docs/create-database-with-mcp-toolbox"/>
+  </head>
+</html>

docs/en/how-to/connect-ide/alloydb_pg_mcp.md

@@ -7,7 +7,7 @@ description: >
 ---
 <html>
   <head>
-    <link rel="canonical" href="https://cloud.google.com/alloydb/docs/pre-built-tools-with-mcp-toolbox"/>
-    <meta http-equiv="refresh" content="0;url=https://cloud.google.com/alloydb/docs/pre-built-tools-with-mcp-toolbox"/>
+    <link rel="canonical" href="https://cloud.google.com/alloydb/docs/connect-ide-using-mcp-toolbox"/>
+    <meta http-equiv="refresh" content="0;url=https://cloud.google.com/alloydb/docs/connect-ide-using-mcp-toolbox"/>
   </head>
 </html>

docs/en/how-to/connect-ide/firestore_mcp.md

@@ -28,18 +28,24 @@ to expose your developer assistant tools to a Firestore instance:
 [claudedesktop]: #configure-your-mcp-client
 [claudecode]: #configure-your-mcp-client
 [geminicli]: #configure-your-mcp-client
-[geminicodeassist]: #configure-your-mcp-client]
+[geminicodeassist]: #configure-your-mcp-client
 
 ## Set up Firestore
 
 1. Create or select a Google Cloud project.
 
-    * [Create a new project](https://cloud.google.com/resource-manager/docs/creating-managing-projects)
-    * [Select an existing project](https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects)
+    * [Create a new
+      project](https://cloud.google.com/resource-manager/docs/creating-managing-projects)
+    * [Select an existing
+      project](https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects)
 
-1. [Enable the Firestore API](https://console.cloud.google.com/apis/library/firestore.googleapis.com) for your project.
+1. [Enable the Firestore
+   API](https://console.cloud.google.com/apis/library/firestore.googleapis.com)
+   for your project.
 
-1. [Create a Firestore database](https://cloud.google.com/firestore/docs/create-database-web-mobile-client-library) if you haven't already.
+1. [Create a Firestore
+   database](https://cloud.google.com/firestore/docs/create-database-web-mobile-client-library)
+   if you haven't already.
 
 1. Set up authentication for your local environment.
 
@@ -56,19 +62,19 @@ to expose your developer assistant tools to a Firestore instance:
    <!-- {x-release-please-start-version} -->
    {{< tabpane persist=header >}}
 {{< tab header="linux/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/linux/amd64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/linux/amd64/toolbox
 {{< /tab >}}
 
 {{< tab header="darwin/arm64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/darwin/arm64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/arm64/toolbox
 {{< /tab >}}
 
 {{< tab header="darwin/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/darwin/amd64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/amd64/toolbox
 {{< /tab >}}
 
 {{< tab header="windows/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/windows/amd64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/windows/amd64/toolbox
 {{< /tab >}}
 {{< /tabpane >}}
     <!-- {x-release-please-end} -->
@@ -247,9 +253,13 @@ curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/windows/amd64/toolb
 {{% /tab %}}
 {{% tab header="Gemini CLI" lang="en" %}}
 
-1.  Install the [Gemini CLI](https://github.com/google-gemini/gemini-cli?tab=readme-ov-file#quickstart).
-1.  In your working directory, create a folder named `.gemini`. Within it, create a `settings.json` file.
-1.  Add the following configuration, replace the environment variables with your values, and then save:
+1. Install the [Gemini
+   CLI](https://github.com/google-gemini/gemini-cli?tab=readme-ov-file#quickstart).
+1. In your working directory, create a folder named `.gemini`. Within it, create
+   a `settings.json` file.
+1. Add the following configuration, replace the environment variables with your
+   values, and then save:
+
     ```json
     {
       "mcpServers": {
@@ -269,10 +279,15 @@ curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/windows/amd64/toolb
 {{% /tab %}}
 {{% tab header="Gemini Code Assist" lang="en" %}}
 
-1.  Install the [Gemini Code Assist](https://marketplace.visualstudio.com/items?itemName=Google.geminicodeassist) extension in Visual Studio Code.
-1.  Enable Agent Mode in Gemini Code Assist chat.
-1.  In your working directory, create a folder named `.gemini`. Within it, create a `settings.json` file.
-1.  Add the following configuration, replace the environment variables with your values, and then save:
+1. Install the [Gemini Code
+   Assist](https://marketplace.visualstudio.com/items?itemName=Google.geminicodeassist)
+   extension in Visual Studio Code.
+1. Enable Agent Mode in Gemini Code Assist chat.
+1. In your working directory, create a folder named `.gemini`. Within it, create
+   a `settings.json` file.
+1. Add the following configuration, replace the environment variables with your
+   values, and then save:
+
     ```json
     {
       "mcpServers": {
@@ -300,12 +315,17 @@ security rules.
 
 The following tools are available to the LLM:
 
-1. **firestore-get-documents**: Gets multiple documents from Firestore by their paths
-1. **firestore-list-collections**: List Firestore collections for a given parent path
+1. **firestore-get-documents**: Gets multiple documents from Firestore by their
+   paths
+1. **firestore-list-collections**: List Firestore collections for a given parent
+   path
 1. **firestore-delete-documents**: Delete multiple documents from Firestore
-1. **firestore-query-collection**: Query documents from a collection with filtering, ordering, and limit options
-1. **firestore-get-rules**: Retrieves the active Firestore security rules for the current project
-1. **firestore-validate-rules**: Validates Firestore security rules syntax and errors
+1. **firestore-query-collection**: Query documents from a collection with
+   filtering, ordering, and limit options
+1. **firestore-get-rules**: Retrieves the active Firestore security rules for
+   the current project
+1. **firestore-validate-rules**: Validates Firestore security rules syntax and
+   errors
 
 {{< notice note >}}
 Prebuilt tools are pre-1.0, so expect some tool changes between versions. LLMs

docs/en/how-to/connect-ide/looker_mcp.md

@@ -44,21 +44,21 @@ to expose your developer assistant tools to a Looker instance:
    v0.10.0+:
 
    <!-- {x-release-please-start-version} -->
-   {{< tabpane persist=header >}}
+{{< tabpane persist=header >}}
 {{< tab header="linux/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/linux/amd64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/linux/amd64/toolbox
 {{< /tab >}}
 
 {{< tab header="darwin/arm64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/darwin/arm64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/arm64/toolbox
 {{< /tab >}}
 
 {{< tab header="darwin/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/darwin/amd64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/amd64/toolbox
 {{< /tab >}}
 
 {{< tab header="windows/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/windows/amd64/toolbox.exe
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/windows/amd64/toolbox.exe
 {{< /tab >}}
 {{< /tabpane >}}
     <!-- {x-release-please-end} -->
@@ -263,10 +263,12 @@ The following tools are available to the LLM:
 1. **get_measures**: list the measures in a given explore
 1. **get_filters**: list the filters in a given explore
 1. **get_parameters**: list the parameters in a given explore
-1. **query**: Run a query
+1. **query**: Run a query and return the data
 1. **query_sql**: Return the SQL generated by Looker for a query
+1. **query_url**: Return a link to the query in Looker for further exploration
 1. **get_looks**: Return the saved Looks that match a title or description
 1. **run_look**: Run a saved Look and return the data
+1. **make_look**: Create a saved Look in Looker and return the URL
 
 {{< notice note >}}
 Prebuilt tools are pre-1.0, so expect some tool changes between versions. LLMs

docs/en/how-to/connect-ide/mssql_mcp.md

@@ -0,0 +1,289 @@
+---
+title: SQL Server using MCP
+type: docs
+weight: 2
+description: "Connect your IDE to SQL Server using Toolbox."
+---
+
+[Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) is an open protocol for connecting Large Language Models (LLMs) to data sources like SQL Server. This guide covers how to use [MCP Toolbox for Databases][toolbox] to expose your developer assistant tools to a SQL Server instance:
+
+* [Cursor][cursor]
+* [Windsurf][windsurf] (Codium)
+* [Visual Studio Code][vscode] (Copilot)
+* [Cline][cline] (VS Code extension)
+* [Claude desktop][claudedesktop]
+* [Claude code][claudecode]
+* [Gemini CLI][geminicli]
+* [Gemini Code Assist][geminicodeassist]
+
+[toolbox]: https://github.com/googleapis/genai-toolbox
+[cursor]: #configure-your-mcp-client
+[windsurf]: #configure-your-mcp-client
+[vscode]: #configure-your-mcp-client
+[cline]: #configure-your-mcp-client
+[claudedesktop]: #configure-your-mcp-client
+[claudecode]: #configure-your-mcp-client
+[geminicli]: #configure-your-mcp-client
+[geminicodeassist]: #configure-your-mcp-client
+
+## Set up the database
+
+1.  [Create or select a SQL Server instance.](https://www.microsoft.com/en-us/sql-server/sql-server-downloads)
+
+## Install MCP Toolbox
+
+1. Download the latest version of Toolbox as a binary. Select the [correct binary](https://github.com/googleapis/genai-toolbox/releases) corresponding to your OS and CPU architecture. You are required to use Toolbox version V0.10.0+:
+
+   <!-- {x-release-please-start-version} -->
+   {{< tabpane persist=header >}}
+{{< tab header="linux/amd64" lang="bash" >}}
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/linux/amd64/toolbox
+{{< /tab >}}
+
+{{< tab header="darwin/arm64" lang="bash" >}}
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/arm64/toolbox
+{{< /tab >}}
+
+{{< tab header="darwin/amd64" lang="bash" >}}
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/amd64/toolbox
+{{< /tab >}}
+
+{{< tab header="windows/amd64" lang="bash" >}}
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/windows/amd64/toolbox.exe
+{{< /tab >}}
+{{< /tabpane >}}
+    <!-- {x-release-please-end} -->
+
+1. Make the binary executable:
+
+    ```bash
+    chmod +x toolbox
+    ```
+
+1. Verify the installation:
+
+    ```bash
+    ./toolbox --version
+    ```
+
+## Configure your MCP Client
+
+{{< tabpane text=true >}}
+{{% tab header="Claude code" lang="en" %}}
+
+1.  Install [Claude Code](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview).
+1.  Create a `.mcp.json` file in your project root if it doesn't exist.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "sqlserver": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mssql","--stdio"],
+          "env": {
+            "MSSQL_HOST": "",
+            "MSSQL_PORT": "",
+            "MSSQL_DATABASE": "",
+            "MSSQL_USER": "",
+            "MSSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+
+1.  Restart Claude code to apply the new configuration.
+{{% /tab %}}
+{{% tab header="Claude desktop" lang="en" %}}
+
+1.  Open [Claude desktop](https://claude.ai/download) and navigate to Settings.
+1.  Under the Developer tab, tap Edit Config to open the configuration file.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "sqlserver": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mssql","--stdio"],
+          "env": {
+            "MSSQL_HOST": "",
+            "MSSQL_PORT": "",
+            "MSSQL_DATABASE": "",
+            "MSSQL_USER": "",
+            "MSSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+
+1.  Restart Claude desktop.
+1.  From the new chat screen, you should see a hammer (MCP) icon appear with the new MCP server available.
+{{% /tab %}}
+{{% tab header="Cline" lang="en" %}}
+
+1.  Open the [Cline](https://github.com/cline/cline) extension in VS Code and tap the **MCP Servers** icon.
+1.  Tap Configure MCP Servers to open the configuration file.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "sqlserver": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mssql","--stdio"],
+          "env": {
+            "MSSQL_HOST": "",
+            "MSSQL_PORT": "",
+            "MSSQL_DATABASE": "",
+            "MSSQL_USER": "",
+            "MSSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+
+1.  You should see a green active status after the server is successfully connected.
+{{% /tab %}}
+{{% tab header="Cursor" lang="en" %}}
+
+1.  Create a `.cursor` directory in your project root if it doesn't exist.
+1.  Create a `.cursor/mcp.json` file if it doesn't exist and open it.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "sqlserver": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mssql","--stdio"],
+          "env": {
+            "MSSQL_HOST": "",
+            "MSSQL_PORT": "",
+            "MSSQL_DATABASE": "",
+            "MSSQL_USER": "",
+            "MSSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+
+1.  Open [Cursor](https://www.cursor.com/) and navigate to **Settings > Cursor Settings > MCP**. You should see a green active status after the server is successfully connected.
+{{% /tab %}}
+{{% tab header="Visual Studio Code (Copilot)" lang="en" %}}
+
+1.  Open [VS Code](https://code.visualstudio.com/docs/copilot/overview) and create a `.vscode` directory in your project root if it doesn't exist.
+1.  Create a `.vscode/mcp.json` file if it doesn't exist and open it.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+    "mcp" : {
+        "servers": {
+        "cloud-sql-sqlserver": {
+            "command": "./PATH/TO/toolbox",
+            "args": ["--prebuilt","cloud-sql-mssql","--stdio"],
+            "env": {
+              "MSSQL_HOST": "",
+              "MSSQL_PORT": "",
+              "MSSQL_DATABASE": "",
+              "MSSQL_USER": "",
+              "MSSQL_PASSWORD": ""
+            }
+         }
+        }
+      }
+    }
+    ```
+{{% /tab %}}
+{{% tab header="Windsurf" lang="en" %}}
+
+1.  Open [Windsurf](https://docs.codeium.com/windsurf) and navigate to the Cascade assistant.
+1.  Tap on the hammer (MCP) icon, then Configure to open the configuration file.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "sqlserver": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mssql","--stdio"],
+          "env": {
+            "MSSQL_HOST": "",
+            "MSSQL_PORT": "",
+            "MSSQL_DATABASE": "",
+            "MSSQL_USER": "",
+            "MSSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+{{% /tab %}}
+{{% tab header="Gemini CLI" lang="en" %}}
+
+1.  Install the [Gemini CLI](https://github.com/google-gemini/gemini-cli?tab=readme-ov-file#quickstart).
+1.  In your working directory, create a folder named `.gemini`. Within it, create a `settings.json` file.
+1.  Add the following configuration, replace the environment variables with your values, and then save:
+
+    ```json
+    {
+      "mcpServers": {
+        "sqlserver": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mssql","--stdio"],
+          "env": {
+            "MSSQL_HOST": "",
+            "MSSQL_PORT": "",
+            "MSSQL_DATABASE": "",
+            "MSSQL_USER": "",
+            "MSSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+{{% /tab %}}
+{{% tab header="Gemini Code Assist" lang="en" %}}
+
+1.  Install the [Gemini Code Assist](https://marketplace.visualstudio.com/items?itemName=Google.geminicodeassist) extension in Visual Studio Code.
+1.  Enable Agent Mode in Gemini Code Assist chat.
+1.  In your working directory, create a folder named `.gemini`. Within it, create a `settings.json` file.
+1.  Add the following configuration, replace the environment variables with your values, and then save:
+
+    ```json
+    {
+      "mcpServers": {
+        "sqlserver": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mssql","--stdio"],
+          "env": {
+            "MSSQL_HOST": "",
+            "MSSQL_PORT": "",
+            "MSSQL_DATABASE": "",
+            "MSSQL_USER": "",
+            "MSSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+{{% /tab %}}
+{{< /tabpane >}}
+
+## Use Tools
+
+Your AI tool is now connected to SQL Server using MCP. Try asking your AI assistant to list tables, create a table, or define and execute other SQL statements.
+
+The following tools are available to the LLM:
+
+1.  **list_tables**: lists tables and descriptions
+1.  **execute_sql**: execute any SQL statement
+
+{{< notice note >}}
+Prebuilt tools are pre-1.0, so expect some tool changes between versions. LLMs will adapt to the tools available, so this shouldn't affect most users.
+{{< /notice >}}

docs/en/how-to/connect-ide/mysql_mcp.md

@@ -0,0 +1,287 @@
+---
+title: MySQL using MCP
+type: docs
+weight: 2
+description: "Connect your IDE to MySQL using Toolbox."
+---
+
+[Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) is an open protocol for connecting Large Language Models (LLMs) to data sources like MySQL. This guide covers how to use [MCP Toolbox for Databases][toolbox] to expose your developer assistant tools to a MySQL instance:
+
+* [Cursor][cursor]
+* [Windsurf][windsurf] (Codium)
+* [Visual Studio Code][vscode] (Copilot)
+* [Cline][cline] (VS Code extension)
+* [Claude desktop][claudedesktop]
+* [Claude code][claudecode]
+* [Gemini CLI][geminicli]
+* [Gemini Code Assist][geminicodeassist]
+
+[toolbox]: https://github.com/googleapis/genai-toolbox
+[cursor]: #configure-your-mcp-client
+[windsurf]: #configure-your-mcp-client
+[vscode]: #configure-your-mcp-client
+[cline]: #configure-your-mcp-client
+[claudedesktop]: #configure-your-mcp-client
+[claudecode]: #configure-your-mcp-client
+[geminicli]: #configure-your-mcp-client
+[geminicodeassist]: #configure-your-mcp-client
+
+## Set up the database
+
+1.  [Create or select a MySQL instance.](https://dev.mysql.com/downloads/installer/)
+
+## Install MCP Toolbox
+
+1. Download the latest version of Toolbox as a binary. Select the [correct binary](https://github.com/googleapis/genai-toolbox/releases) corresponding to your OS and CPU architecture. You are required to use Toolbox version V0.10.0+:
+
+   <!-- {x-release-please-start-version} -->
+   {{< tabpane persist=header >}}
+{{< tab header="linux/amd64" lang="bash" >}}
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/linux/amd64/toolbox
+{{< /tab >}}
+
+{{< tab header="darwin/arm64" lang="bash" >}}
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/arm64/toolbox
+{{< /tab >}}
+
+{{< tab header="darwin/amd64" lang="bash" >}}
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/amd64/toolbox
+{{< /tab >}}
+
+{{< tab header="windows/amd64" lang="bash" >}}
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/windows/amd64/toolbox.exe
+{{< /tab >}}
+{{< /tabpane >}}
+    <!-- {x-release-please-end} -->
+
+1. Make the binary executable:
+
+    ```bash
+    chmod +x toolbox
+    ```
+
+1. Verify the installation:
+
+    ```bash
+    ./toolbox --version
+    ```
+
+## Configure your MCP Client
+
+{{< tabpane text=true >}}
+{{% tab header="Claude code" lang="en" %}}
+
+1.  Install [Claude Code](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview).
+1.  Create a `.mcp.json` file in your project root if it doesn't exist.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "mysql": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt", "mysql", "--stdio"],
+          "env": {
+            "MYSQL_HOST": "",
+            "MYSQL_PORT": "",
+            "MYSQL_DATABASE": "",
+            "MYSQL_USER": "",
+            "MYSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+
+1.  Restart Claude code to apply the new configuration.
+{{% /tab %}}
+{{% tab header="Claude desktop" lang="en" %}}
+
+1.  Open [Claude desktop](https://claude.ai/download) and navigate to Settings.
+1.  Under the Developer tab, tap Edit Config to open the configuration file.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "mysql": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt", "mysql", "--stdio"],
+          "env": {
+            "MYSQL_HOST": "",
+            "MYSQL_PORT": "",
+            "MYSQL_DATABASE": "",
+            "MYSQL_USER": "",
+            "MYSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+
+1.  Restart Claude desktop.
+1.  From the new chat screen, you should see a hammer (MCP) icon appear with the new MCP server available.
+{{% /tab %}}
+{{% tab header="Cline" lang="en" %}}
+
+1.  Open the [Cline](https://github.com/cline/cline) extension in VS Code and tap the **MCP Servers** icon.
+1.  Tap Configure MCP Servers to open the configuration file.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "mysql": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt", "mysql", "--stdio"],
+          "env": {
+            "MYSQL_HOST": "",
+            "MYSQL_PORT": "",
+            "MYSQL_DATABASE": "",
+            "MYSQL_USER": "",
+            "MYSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+
+1.  You should see a green active status after the server is successfully connected.
+{{% /tab %}}
+{{% tab header="Cursor" lang="en" %}}
+
+1.  Create a `.cursor` directory in your project root if it doesn't exist.
+1.  Create a `.cursor/mcp.json` file if it doesn't exist and open it.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "mysql": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt", "mysql", "--stdio"],
+          "env": {
+            "MYSQL_HOST": "",
+            "MYSQL_PORT": "",
+            "MYSQL_DATABASE": "",
+            "MYSQL_USER": "",
+            "MYSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+
+1.  Open [Cursor](https://www.cursor.com/) and navigate to **Settings > Cursor Settings > MCP**. You should see a green active status after the server is successfully connected.
+{{% /tab %}}
+{{% tab header="Visual Studio Code (Copilot)" lang="en" %}}
+
+1.  Open [VS Code](https://code.visualstudio.com/docs/copilot/overview) and create a `.vscode` directory in your project root if it doesn't exist.
+1.  Create a `.vscode/mcp.json` file if it doesn't exist and open it.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "mysql": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mysql","--stdio"],
+          "env": {
+            "MYSQL_HOST": "",
+            "MYSQL_PORT": "",
+            "MYSQL_DATABASE": "",
+            "MYSQL_USER": "",
+            "MYSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+{{% /tab %}}
+{{% tab header="Windsurf" lang="en" %}}
+
+1.  Open [Windsurf](https://docs.codeium.com/windsurf) and navigate to the Cascade assistant.
+1.  Tap on the hammer (MCP) icon, then Configure to open the configuration file.
+1.  Add the following configuration, replace the environment variables with your values, and save:
+
+    ```json
+    {
+      "mcpServers": {
+        "mysql": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mysql","--stdio"],
+          "env": {
+            "MYSQL_HOST": "",
+            "MYSQL_PORT": "",
+            "MYSQL_DATABASE": "",
+            "MYSQL_USER": "",
+            "MYSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+{{% /tab %}}
+{{% tab header="Gemini CLI" lang="en" %}}
+
+1.  Install the [Gemini CLI](https://github.com/google-gemini/gemini-cli?tab=readme-ov-file#quickstart).
+1.  In your working directory, create a folder named `.gemini`. Within it, create a `settings.json` file.
+1.  Add the following configuration, replace the environment variables with your values, and then save:
+
+    ```json
+    {
+      "mcpServers": {
+        "mysql": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mysql","--stdio"],
+          "env": {
+            "MYSQL_HOST": "",
+            "MYSQL_PORT": "",
+            "MYSQL_DATABASE": "",
+            "MYSQL_USER": "",
+            "MYSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+{{% /tab %}}
+{{% tab header="Gemini Code Assist" lang="en" %}}
+
+1.  Install the [Gemini Code Assist](https://marketplace.visualstudio.com/items?itemName=Google.geminicodeassist) extension in Visual Studio Code.
+1.  Enable Agent Mode in Gemini Code Assist chat.
+1.  In your working directory, create a folder named `.gemini`. Within it, create a `settings.json` file.
+1.  Add the following configuration, replace the environment variables with your values, and then save:
+
+    ```json
+    {
+      "mcpServers": {
+        "mysql": {
+          "command": "./PATH/TO/toolbox",
+          "args": ["--prebuilt","mysql","--stdio"],
+          "env": {
+            "MYSQL_HOST": "",
+            "MYSQL_PORT": "",
+            "MYSQL_DATABASE": "",
+            "MYSQL_USER": "",
+            "MYSQL_PASSWORD": ""
+          }
+        }
+      }
+    }
+    ```
+{{% /tab %}}
+{{< /tabpane >}}
+
+## Use Tools
+
+Your AI tool is now connected to MySQL using MCP. Try asking your AI assistant to list tables, create a table, or define and execute other SQL statements.
+
+The following tools are available to the LLM:
+
+1.  **list_tables**: lists tables and descriptions
+1.  **execute_sql**: execute any SQL statement
+
+{{< notice note >}}
+Prebuilt tools are pre-1.0, so expect some tool changes between versions. LLMs will adapt to the tools available, so this shouldn't affect most users.
+{{< /notice >}}

docs/en/how-to/connect-ide/postgres_mcp.md

@@ -52,19 +52,19 @@ Omni](https://cloud.google.com/alloydb/omni/current/docs/overview).
    <!-- {x-release-please-start-version} -->
    {{< tabpane persist=header >}}
 {{< tab header="linux/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/linux/amd64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/linux/amd64/toolbox
 {{< /tab >}}
 
 {{< tab header="darwin/arm64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/darwin/arm64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/arm64/toolbox
 {{< /tab >}}
 
 {{< tab header="darwin/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/darwin/amd64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/darwin/amd64/toolbox
 {{< /tab >}}
 
 {{< tab header="windows/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.10.0/windows/amd64/toolbox.exe
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/windows/amd64/toolbox.exe
 {{< /tab >}}
 {{< /tabpane >}}
     <!-- {x-release-please-end} -->

docs/en/how-to/connect_via_mcp.md

@@ -28,8 +28,9 @@ Toolbox currently supports the following versions of MCP specification:
 
 The auth implementation in Toolbox is not supported in MCP's auth specification.
 This includes:
-  * [Authenticated Parameters](../resources/tools/_index.md#authenticated-parameters)
-  * [Authorized Invocations](../resources/tools/_index.md#authorized-invocations)
+
+* [Authenticated Parameters](../resources/tools/#authenticated-parameters)
+* [Authorized Invocations](../resources/tools/#authorized-invocations)
 
 ## Connecting to Toolbox with an MCP client
 
@@ -39,7 +40,7 @@ This includes:
 MCP is only compatible with Toolbox version 0.3.0 and above.
 {{< /notice >}}
 
-1. [Install](../getting-started/introduction/_index.md#installing-the-server)
+1. [Install](../getting-started/introduction/#installing-the-server)
    Toolbox version 0.3.0+.
 
 1. Make sure you've set up and initialized your database.
@@ -62,7 +63,8 @@ remote HTTP server. Logs will be set to the `warn` level by default. `debug` and
 `info` logs are not supported with stdio.
 
 {{< notice note >}}
-Toolbox enables dynamic reloading by default. To disable, use the `--disable-reload` flag.
+Toolbox enables dynamic reloading by default. To disable, use the
+`--disable-reload` flag.
 {{< /notice >}}
 
 ### Connecting via HTTP
@@ -131,7 +133,7 @@ testing and debugging Toolbox server.
    You should be able to inspect your toolbox tools!
 {{% /tab %}}
 {{% tab header="HTTP with SSE (deprecated)" lang="en" %}}
-1. [Run Toolbox](../getting-started/introduction/_index.md#running-the-server).
+1. [Run Toolbox](../getting-started/introduction/#running-the-server).
 
 1. In a separate terminal, run Inspector directly through `npx`:
 
@@ -148,7 +150,7 @@ testing and debugging Toolbox server.
    tools!
 {{% /tab %}}
 {{% tab header="Streamable HTTP" lang="en" %}}
-1. [Run Toolbox](../getting-started/introduction/_index.md#running-the-server).
+1. [Run Toolbox](../getting-started/introduction/#running-the-server).
 
 1. In a separate terminal, run Inspector directly through `npx`:
 

docs/en/how-to/deploy_toolbox.md

@@ -79,7 +79,7 @@ database are in the same VPC network.
 
 Create a `tools.yaml` file that contains your configuration for Toolbox. For
 details, see the
-[configuration](https://googleapis.github.io/genai-toolbox/resources/sources/)
+[configuration](../resources/sources/)
 section.
 
 ## Deploy to Cloud Run
@@ -125,7 +125,7 @@ section.
         --region us-central1 \
         --set-secrets "/app/tools.yaml=tools:latest" \
         --args="--tools-file=/app/tools.yaml","--address=0.0.0.0","--port=8080" \
-        # TODO(dev): update the following to match your VPC if necessary 
+        # TODO(dev): update the following to match your VPC if necessary
         --network default \
         --subnet default
         # --allow-unauthenticated # https://cloud.google.com/run/docs/authenticating/public#gcloud

docs/en/how-to/use-toolbox-ui/index.md

@@ -0,0 +1,106 @@
+---
+title: "Toolbox UI"
+type: docs
+weight: 1
+description: >
+  How to effectively use Toolbox UI.
+---
+
+Toolbox UI is a built-in web interface that allows users to visually inspect and test out configured resources such as tools and toolsets.
+
+## Launching Toolbox UI
+
+To launch Toolbox's interactive UI, use the `--ui` flag.
+
+```sh
+./toolbox --ui
+```
+
+Toolbox UI will be served from the same host and port as the Toolbox Server, with the `/ui` suffix. Once Toolbox
+is launched, the following INFO log with Toolbox UI's url will be shown:
+
+```bash
+INFO "Toolbox UI is up and running at: http://localhost:5000/ui"
+```
+
+## Navigating the Tools Page
+
+The tools page shows all tools loaded from your configuration file. This corresponds to the default toolset (represented by an empty string). Each tool's name on this page will exactly match its name in the configuration 
+file.
+
+To view details for a specific tool, click on the tool name. The main content area will be populated
+with the tool name, description, and available parameters.
+
+![Tools Page](./tools.png)
+
+### Invoking a Tool
+
+1. Click on a Tool
+2. Enter appropriate parameters in each parameter field
+3. Click "Run Tool"
+4. Done! Your results will appear in the response field
+5. (Optional) Uncheck "Prettify JSON" to format the response as plain text
+
+![Run Tool Demo GIF](./run-tool.gif)
+
+### Optional Parameters
+
+Toolbox allows users to add [optional parameters](../../resources/tools/#basic-parameters) with or without a default value. 
+
+To exclude a parameter, uncheck the box to the right of an associated parameter, and that parameter will not be
+included in the request body. If the parameter is not sent, Toolbox will either use it as `nil` value or the `default` value, if configured. If the parameter is required, Toolbox will throw an error.
+
+When the box is checked, parameter will be sent exactly as entered in the response field (e.g. empty string).
+
+![Optional Parameter checked example](./optional-param-checked.png)
+
+![Optional Parameter unchecked example](./optional-param-unchecked.png)
+
+### Editing Headers
+
+To edit headers, press the "Edit Headers" button to display the header modal. Within this modal,
+users can make direct edits by typing into the header's text area. 
+
+Toolbox UI validates that the headers are in correct JSON format. Other header-related errors (e.g.,
+incorrect header names or values required by the tool) will be reported in the Response section 
+after running the tool.
+
+![Edit Headers](./edit-headers.png)
+
+#### Google OAuth
+
+Currently, Toolbox supports Google OAuth 2.0 as an AuthService, which allows tools to utilize 
+authorized parameters. When a tool uses an authorized parameter, the parameter will be displayed
+but not editable, as it will be populated from the authentication token.  
+
+To provide the token, add your Google OAuth ID Token to the request header using the "Edit Headers"
+button and modal described above. The key should be the name of your AuthService as defined in 
+your tool configuration file, suffixed with `_token`. The value should be your ID token as a string.
+
+1. Select a tool that requires [authenticated parameters]()
+2. The auth parameter's text field is greyed out. This is because it cannot be entered manually and will
+be parsed from the resolved auth token
+3. To update request headers with the token, select "Edit Headers"
+4. Checkout the dropdown "How to extract Google OAuth ID Token manually" for guidance on retrieving ID token
+5. Paste the request header
+6. Click "Save"
+7. Click "Run Tool"
+
+```json
+{
+  "Content-Type": "application/json",
+  "my-google-auth_token": "YOUR_ID_TOKEN_HERE"
+}
+```
+
+![Using Authenticated Parameter GIF](./edit-headers.gif)
+
+## Navigating the Toolsets Page
+
+Through the toolsets page, users can search for a specific toolset to retrieve tools from. Simply
+enter the toolset name in the search bar, and press "Enter" to retrieve the associated tools.
+
+If the toolset name is not defined within the tools configuration file, an error message will be 
+displayed.
+
+![Toolsets Page](./toolsets.png)

docs/en/resources/authServices/_index.md

@@ -3,11 +3,11 @@ title: "AuthServices"
 type: docs
 weight: 1
 description: >
-  AuthServices represent services that handle authentication and authorization. 
+  AuthServices represent services that handle authentication and authorization.
 ---
 
 AuthServices represent services that handle authentication and authorization. It
-can primarily be used by [Tools](../tools) in two different ways:
+can primarily be used by [Tools](../tools/) in two different ways:
 
 - [**Authorized Invocation**][auth-invoke] is when a tool
   is validated by the auth service before the call can be invoked. Toolbox

docs/en/resources/authServices/google.md

@@ -3,7 +3,7 @@ title: "Google Sign-In"
 type: docs
 weight: 1
 description: >
-  Use Google Sign-In for Oauth 2.0 flow and token lifecycle. 
+  Use Google Sign-In for Oauth 2.0 flow and token lifecycle.
 ---
 
 ## Getting Started

docs/en/resources/sources/alloydb-pg.md

@@ -33,6 +33,14 @@ cluster][alloydb-free-trial].
 - [`postgres-execute-sql`](../tools/postgres/postgres-execute-sql.md)  
   Run parameterized SQL statements in AlloyDB Postgres.
 
+### Pre-built Configurations
+
+- [AlloyDB using MCP](https://googleapis.github.io/genai-toolbox/how-to/connect-ide/alloydb_pg_mcp/)  
+Connect your IDE to AlloyDB using Toolbox.
+
+- [AlloyDB Admin API using MCP](https://googleapis.github.io/genai-toolbox/how-to/connect-ide/alloydb_pg_admin_mcp/)  
+Create your AlloyDB database with MCP Toolbox.
+
 ## Requirements
 
 ### IAM Permissions

docs/en/resources/sources/bigquery.md

@@ -54,6 +54,11 @@ avoiding full table scans or complex filters.
 - [`bigquery-list-table-ids`](../tools/bigquery/bigquery-list-table-ids.md)  
   List tables in a given dataset.
 
+### Pre-built Configurations
+
+- [BigQuery using MCP](https://googleapis.github.io/genai-toolbox/how-to/connect-ide/bigquery_mcp/)  
+Connect your IDE to BigQuery using Toolbox.
+
 ## Requirements
 
 ### IAM Permissions

docs/en/resources/sources/cloud-sql-mssql.md

@@ -27,6 +27,11 @@ to a database by following these instructions][csql-mssql-connect].
 - [`mssql-execute-sql`](../tools/mssql/mssql-execute-sql.md)  
   Run parameterized SQL Server queries in Cloud SQL for SQL Server.
 
+### Pre-built Configurations
+
+- [Cloud SQL for SQL Server using MCP](https://googleapis.github.io/genai-toolbox/how-to/connect-ide/cloud_sql_mssql_mcp/)  
+Connect your IDE to Cloud SQL for SQL Server using Toolbox.
+
 ## Requirements
 
 ### IAM Permissions

docs/en/resources/sources/cloud-sql-mysql.md

@@ -28,6 +28,11 @@ to a database by following these instructions][csql-mysql-quickstart].
 - [`mysql-execute-sql`](../tools/mysql/mysql-execute-sql.md)  
   Run parameterized SQL queries in Cloud SQL for MySQL.
 
+### Pre-built Configurations
+
+- [Cloud SQL for MySQL using MCP](https://googleapis.github.io/genai-toolbox/how-to/connect-ide/cloud_sql_mysql_mcp/)  
+Connect your IDE to Cloud SQL for MySQL using Toolbox.
+
 ## Requirements
 
 ### IAM Permissions

docs/en/resources/sources/cloud-sql-pg.md

@@ -28,6 +28,12 @@ to a database by following these instructions][csql-pg-quickstart].
 - [`postgres-execute-sql`](../tools/postgres/postgres-execute-sql.md)  
   Run parameterized SQL statements in PostgreSQL.
 
+### Pre-built Configurations
+
+- [Cloud SQL for Postgres using MCP](https://googleapis.github.io/genai-toolbox/how-to/connect-ide/cloud_sql_pg_mcp/)  
+Connect your IDE to Cloud SQL for Postgres using Toolbox.
+
+
 ## Requirements
 
 ### IAM Permissions

docs/en/resources/sources/dataplex.md

@@ -8,9 +8,15 @@ description: >
 
 # Dataplex Source
 
-[Dataplex][dataplex-docs] Universal Catalog is a unified, intelligent governance solution for data and AI assets in Google Cloud. Dataplex Universal Catalog powers AI, analytics, and business intelligence at scale.
+[Dataplex][dataplex-docs] Universal Catalog is a unified, intelligent governance
+solution for data and AI assets in Google Cloud. Dataplex Universal Catalog
+powers AI, analytics, and business intelligence at scale.
 
-At the heart of these governance capabilities is a catalog that contains a centralized inventory of the data assets in your organization. Dataplex Universal Catalog holds business, technical, and runtime metadata for all of your data. It helps you discover relationships and semantics in the metadata by applying artificial intelligence and machine learning.
+At the heart of these governance capabilities is a catalog that contains a
+centralized inventory of the data assets in your organization. Dataplex
+Universal Catalog holds business, technical, and runtime metadata for all of
+your data. It helps you discover relationships and semantics in the metadata by
+applying artificial intelligence and machine learning.
 
 [dataplex-docs]: https://cloud.google.com/dataplex/docs
 
@@ -25,13 +31,217 @@ sources:
 
 ## Sample System Prompt
 
-You can use the following system prompt as "Custom Instructions" in your client application.
+You can use the following system prompt as "Custom Instructions" in your client
+application.
 
 ```
-Whenever you will receive response from dataplex_search_entries tool decide what do to by following these steps:
+# Objective
+Your primary objective is to help discover, organize and manage metadata related to data assets. 
+
+# Tone and Style
+1. Adopt the persona of a senior subject matter expert
+2. Your communication style must be:
+    1. Concise: Always favor brevity.
+    2. Direct: Avoid greetings (e.g., "Hi there!", "Certainly!"). Get straight to the point.  
+        Example (Incorrect): Hi there! I see that you are looking for...  
+        Example (Correct): This problem likely stems from...
+3. Do not reiterate or summarize the question in the answer.
+4. Crucially, always convey a tone of uncertainty and caution. Since you are interpreting metadata and have no way to externally verify your answers, never express complete confidence. Frame your responses as interpretations based solely on the provided metadata. Use a suggestive tone, not a prescriptive one:  
+    Example (Correct): "The entry describes..."  
+    Example (Correct): "According to catalog,..."  
+    Example (Correct): "Based on the metadata,..."  
+    Example (Correct): "Based on the search results,..."  
+5. Do not make assumptions
+
+# Data Model
+## Entries
+Entry represents a specific data asset. Entry acts as a metadata record for something that is managed by Catalog, such as:
+
+- A BigQuery table or dataset
+- A Cloud Storage bucket or folder
+- An on-premises SQL table
+
+## Aspects
+While the Entry itself is a container, the rich descriptive information about the asset (e.g., schema, data types, business descriptions, classifications) is stored in associated components called Aspects. Aspects are created based on pre-defined blueprints known as Aspect Types.
+
+## Aspect Types
+Aspect Type is a reusable template that defines the schema for a set of metadata fields. Think of an Aspect Type as a structure for the kind of metadata that is organized in the catalog within the Entry. 
+
+Examples:
+- projects/dataplex-types/locations/global/aspectTypes/analytics-hub-exchange
+- projects/dataplex-types/locations/global/aspectTypes/analytics-hub
+- projects/dataplex-types/locations/global/aspectTypes/analytics-hub-listing
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-connection
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-data-policy
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-dataset
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-model
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-policy
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-routine
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-row-access-policy
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-table
+- projects/dataplex-types/locations/global/aspectTypes/bigquery-view
+- projects/dataplex-types/locations/global/aspectTypes/cloud-bigtable-instance
+- projects/dataplex-types/locations/global/aspectTypes/cloud-bigtable-table
+- projects/dataplex-types/locations/global/aspectTypes/cloud-spanner-database
+- projects/dataplex-types/locations/global/aspectTypes/cloud-spanner-instance
+- projects/dataplex-types/locations/global/aspectTypes/cloud-spanner-table
+- projects/dataplex-types/locations/global/aspectTypes/cloud-spanner-view
+- projects/dataplex-types/locations/global/aspectTypes/cloudsql-database
+- projects/dataplex-types/locations/global/aspectTypes/cloudsql-instance
+- projects/dataplex-types/locations/global/aspectTypes/cloudsql-schema
+- projects/dataplex-types/locations/global/aspectTypes/cloudsql-table
+- projects/dataplex-types/locations/global/aspectTypes/cloudsql-view
+- projects/dataplex-types/locations/global/aspectTypes/contacts
+- projects/dataplex-types/locations/global/aspectTypes/dataform-code-asset
+- projects/dataplex-types/locations/global/aspectTypes/dataform-repository
+- projects/dataplex-types/locations/global/aspectTypes/dataform-workspace
+- projects/dataplex-types/locations/global/aspectTypes/dataproc-metastore-database
+- projects/dataplex-types/locations/global/aspectTypes/dataproc-metastore-service
+- projects/dataplex-types/locations/global/aspectTypes/dataproc-metastore-table
+- projects/dataplex-types/locations/global/aspectTypes/data-product
+- projects/dataplex-types/locations/global/aspectTypes/data-quality-scorecard
+- projects/dataplex-types/locations/global/aspectTypes/external-connection
+- projects/dataplex-types/locations/global/aspectTypes/overview
+- projects/dataplex-types/locations/global/aspectTypes/pubsub-topic
+- projects/dataplex-types/locations/global/aspectTypes/schema
+- projects/dataplex-types/locations/global/aspectTypes/sensitive-data-protection-job-result
+- projects/dataplex-types/locations/global/aspectTypes/sensitive-data-protection-profile
+- projects/dataplex-types/locations/global/aspectTypes/sql-access
+- projects/dataplex-types/locations/global/aspectTypes/storage-bucket
+- projects/dataplex-types/locations/global/aspectTypes/storage-folder
+- projects/dataplex-types/locations/global/aspectTypes/storage
+- projects/dataplex-types/locations/global/aspectTypes/usage
+
+## Entry Types
+Every Entry must conform to an Entry Type. The Entry Type acts as a template, defining the structure, required aspects, and constraints for Entries of that type. 
+
+Examples:
+- projects/dataplex-types/locations/global/entryTypes/analytics-hub-exchange
+- projects/dataplex-types/locations/global/entryTypes/analytics-hub-listing
+- projects/dataplex-types/locations/global/entryTypes/bigquery-connection
+- projects/dataplex-types/locations/global/entryTypes/bigquery-data-policy
+- projects/dataplex-types/locations/global/entryTypes/bigquery-dataset
+- projects/dataplex-types/locations/global/entryTypes/bigquery-model
+- projects/dataplex-types/locations/global/entryTypes/bigquery-routine
+- projects/dataplex-types/locations/global/entryTypes/bigquery-row-access-policy
+- projects/dataplex-types/locations/global/entryTypes/bigquery-table
+- projects/dataplex-types/locations/global/entryTypes/bigquery-view
+- projects/dataplex-types/locations/global/entryTypes/cloud-bigtable-instance
+- projects/dataplex-types/locations/global/entryTypes/cloud-bigtable-table
+- projects/dataplex-types/locations/global/entryTypes/cloud-spanner-database
+- projects/dataplex-types/locations/global/entryTypes/cloud-spanner-instance
+- projects/dataplex-types/locations/global/entryTypes/cloud-spanner-table
+- projects/dataplex-types/locations/global/entryTypes/cloud-spanner-view
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-mysql-database
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-mysql-instance
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-mysql-table
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-mysql-view
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-postgresql-database
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-postgresql-instance
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-postgresql-schema
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-postgresql-table
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-postgresql-view
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-sqlserver-database
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-sqlserver-instance
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-sqlserver-schema
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-sqlserver-table
+- projects/dataplex-types/locations/global/entryTypes/cloudsql-sqlserver-view
+- projects/dataplex-types/locations/global/entryTypes/dataform-code-asset
+- projects/dataplex-types/locations/global/entryTypes/dataform-repository
+- projects/dataplex-types/locations/global/entryTypes/dataform-workspace
+- projects/dataplex-types/locations/global/entryTypes/dataproc-metastore-database
+- projects/dataplex-types/locations/global/entryTypes/dataproc-metastore-service
+- projects/dataplex-types/locations/global/entryTypes/dataproc-metastore-table
+- projects/dataplex-types/locations/global/entryTypes/pubsub-topic
+- projects/dataplex-types/locations/global/entryTypes/storage-bucket
+- projects/dataplex-types/locations/global/entryTypes/storage-folder
+- projects/dataplex-types/locations/global/entryTypes/vertexai-dataset
+- projects/dataplex-types/locations/global/entryTypes/vertexai-feature-group
+- projects/dataplex-types/locations/global/entryTypes/vertexai-feature-online-store
+
+## Entry Groups
+Entries are organized within Entry Groups, which are logical groupings of Entries. An Entry Group acts as a namespace for its Entries.
+
+## Entry Links
+Entries can be linked together using EntryLinks to represent relationships between data assets (e.g. foreign keys).
+
+# Tool instructions
+## Tool: dataplex_search_entries
+## General
+- Do not try to search within search results on your own.
+- Do not fetch multiple pages of results unless explicitly asked.
+
+## Search syntax
+
+### Simple search
+In its simplest form, a search query consists of a single predicate. Such a predicate can match several pieces of metadata:
+
+- A substring of a name, display name, or description of a resource
+- A substring of the type of a resource
+- A substring of a column name (or nested column name) in the schema of a resource
+- A substring of a project ID
+- A string from an overview description
+
+For example, the predicate foo matches the following resources:
+- Resource with the name foo.bar
+- Resource with the display name Foo Bar
+- Resource with the description This is the foo script
+- Resource with the exact type foo
+- Column foo_bar in the schema of a resource
+- Nested column foo_bar in the schema of a resource
+- Project prod-foo-bar
+- Resource with an overview containing the word foo
+
+
+### Qualified predicates
+You can qualify a predicate by prefixing it with a key that restricts the matching to a specific piece of metadata:
+- An equal sign (=) restricts the search to an exact match.
+- A colon (:) after the key matches the predicate to either a substring or a token within the value in the search results.
+
+Tokenization splits the stream of text into a series of tokens, with each token usually corresponding to a single word. For example:
+- name:foo selects resources with names that contain the foo substring, like foo1 and barfoo.
+- description:foo selects resources with the foo token in the description, like bar and foo.
+- location=foo matches resources in a specified location with foo as the location name.
+
+The predicate keys type, system, location, and orgid support only the exact match (=) qualifier, not the substring qualifier (:). For example, type=foo or orgid=number.
+
+Search syntax supports the following qualifiers:
+- "name:x" - Matches x as a substring of the resource ID.
+- "displayname:x" - Match x as a substring of the resource display name.
+- "column:x" - Matches x as a substring of the column name (or nested column name) in the schema of the resource.
+- "description:x" - Matches x as a token in the resource description.
+- "label:bar" - Matches BigQuery resources that have a label (with some value) and the label key has bar as a substring.
+- "label=bar" - Matches BigQuery resources that have a label (with some value) and the label key equals bar as a string.
+- "label:bar:x" - Matches x as a substring in the value of a label with a key bar attached to a BigQuery resource.
+- "label=foo:bar" - Matches BigQuery resources where the key equals foo and the key value equals bar.
+- "label.foo=bar" - Matches BigQuery resources where the key equals foo and the key value equals bar.
+- "label.foo" - Matches BigQuery resources that have a label whose key equals foo as a string.
+- "type=TYPE" - Matches resources of a specific entry type or its type alias.
+- "projectid:bar" - Matches resources within Google Cloud projects that match bar as a substring in the ID.
+- "parent:x" - Matches x as a substring of the hierarchical path of a resource. The parent path is a fully_qualified_name of the parent resource.
+- "orgid=number" - Matches resources within a Google Cloud organization with the exact ID value of the number.
+- "system=SYSTEM" - Matches resources from a specified system. For example, system=bigquery matches BigQuery resources.
+- "location=LOCATION" - Matches resources in a specified location with an exact name. For example, location=us-central1 matches assets hosted in Iowa. BigQuery Omni assets support this qualifier by using the BigQuery Omni location name. For example, location=aws-us-east-1 matches BigQuery Omni assets in Northern Virginia.
+- "createtime" -
+Finds resources that were created within, before, or after a given date or time. For example "createtime:2019-01-01" matches resources created on 2019-01-01. 
+- "updatetime" - Finds resources that were updated within, before, or after a given date or time. For example "updatetime>2019-01-01" matches resources updated after 2019-01-01.
+- "fully_qualified_name:x" - Matches x as a substring of fully_qualified_name.
+- "fully_qualified_name=x" - Matches x as fully_qualified_name.
+
+### Logical operators
+A query can consist of several predicates with logical operators. If you don't specify an operator, logical AND is implied. For example, foo bar returns resources that match both predicate foo and predicate bar.
+Logical AND and logical OR are supported. For example, foo OR bar.
+
+You can negate a predicate with a - (hyphen) or NOT prefix. For example, -name:foo returns resources with names that don't match the predicate foo.
+Logical operators aren't case-sensitive. For example, both or and OR are acceptable.
+
+### Request
+1. Always try to rewrite the prompt using search syntax.
+
+### Response
 1. If there are multiple search results found
-    1.1. Present the list of search results
-    1.2. Format the output in nested ordered list, for example:
+    1. Present the list of search results
+    2. Format the output in nested ordered list, for example:  
     Given
     ```
     {
@@ -68,14 +278,19 @@ Whenever you will receive response from dataplex_search_entries tool decide what
         - location: us-central1
         - description: Table contains list of best customers.
     ```
-    1.3. Ask to select one of the presented search results
+    3. Ask to select one of the presented search results
 2. If there is only one search result found
-    2.1. Present the search result immediately.
+    1. Present the search result immediately.
 3. If there are no search result found
-    3.1. Explain that no search result was found
-    3.2. Suggest to provide a more specific search query.
+    1. Explain that no search result was found
+    2. Suggest to provide a more specific search query.
 
-Do not try to search within search results on your own.
+## Tool: dataplex_lookup_entry
+### Request
+1. Always try to limit the size of the response by specifying `aspect_types` parameter. Make sure to include to select view=CUSTOM when using aspect_types parameter.
+2. If you do not know the name of the entry, use `dataplex_search_entries` tool
+### Response
+1. Unless asked for a specific aspect, respond with all aspects attached to the entry.
 ```
 
 ## Reference
@@ -83,4 +298,4 @@ Do not try to search within search results on your own.
 | **field** | **type** | **required** | **description**                                                                  |
 |-----------|:--------:|:------------:|----------------------------------------------------------------------------------|
 | kind      |  string  |     true     | Must be "dataplex".                                                              |
-| project   |  string  |     true     | Id of the GCP project used for quota and billing purposes (e.g. "my-project-id").|
+| project   |  string  |     true     | ID of the GCP project used for quota and billing purposes (e.g. "my-project-id").|

docs/en/resources/sources/firestore.md

@@ -33,9 +33,13 @@ with [Firestore][firestore-docs].
 In addition to [setting the ADC for your server][set-adc], you need to ensure
 the IAM identity has been given the correct IAM permissions for accessing
 Firestore. Common roles include:
+
 - `roles/datastore.user` - Read and write access to Firestore
 - `roles/datastore.viewer` - Read-only access to Firestore
-- `roles/firebaserules.admin` - Full management of Firebase Security Rules for Firestore. This role is required for operations that involve creating, updating, or managing Firestore security rules (see [Firebase Security Rules roles][firebaserules-roles])
+- `roles/firebaserules.admin` - Full management of Firebase Security Rules for
+  Firestore. This role is required for operations that involve creating,
+  updating, or managing Firestore security rules (see [Firebase Security Rules
+  roles][firebaserules-roles])
 
 See [Firestore access control][firestore-iam] for more information on
 applying IAM permissions and roles to an identity.
@@ -44,7 +48,8 @@ applying IAM permissions and roles to an identity.
 [adc]: https://cloud.google.com/docs/authentication#adc
 [set-adc]: https://cloud.google.com/docs/authentication/provide-credentials-adc
 [firestore-iam]: https://cloud.google.com/firestore/docs/security/iam
-[firebaserules-roles]: https://cloud.google.com/iam/docs/roles-permissions/firebaserules
+[firebaserules-roles]:
+    https://cloud.google.com/iam/docs/roles-permissions/firebaserules
 
 ### Database Selection
 

docs/en/resources/sources/looker.md

@@ -21,7 +21,8 @@ in the cloud, on GCP, or on premises.
 This source only uses API authentication. You will need to
 [create an API user][looker-user] to login to Looker.
 
-[looker-user]: https://cloud.google.com/looker/docs/api-auth#authentication_with_an_sdk
+[looker-user]:
+    https://cloud.google.com/looker/docs/api-auth#authentication_with_an_sdk
 
 ## Example
 
@@ -36,9 +37,10 @@ sources:
         timeout: 600s
 ```
 
-The Looker base url will look like "https://looker.example.com", don't include a
-trailing "/". In some cases, especially if your Looker is deployed on-premises,
-you may need to add the API port numner like "https://looker.example.com:19999".
+The Looker base url will look like "https://looker.example.com", don't include
+a trailing "/". In some cases, especially if your Looker is deployed
+on-premises, you may need to add the API port numner like
+"https://looker.example.com:19999".
 
 Verify ssl should almost always be "true" (all lower case) unless you are using
 a self-signed ssl certificate for the Looker server. Anything other than "true"

docs/en/resources/sources/mongodb.md

@@ -9,7 +9,8 @@ description: >
 
 ## About
 
-[MongoDB][mongodb-docs] is a popular NoSQL database that stores data in flexible, JSON-like documents, making it easy to develop and scale applications.
+[MongoDB][mongodb-docs] is a popular NoSQL database that stores data in
+flexible, JSON-like documents, making it easy to develop and scale applications.
 
 [mongodb-docs]: https://www.mongodb.com/docs/atlas/getting-started/
 

docs/en/resources/sources/postgres.md

@@ -23,6 +23,11 @@ reputation for reliability, feature robustness, and performance.
 - [`postgres-execute-sql`](../tools/postgres/postgres-execute-sql.md)  
   Run parameterized SQL statements in PostgreSQL.
 
+### Pre-built Configurations
+
+- [PostgreSQL using MCP](https://googleapis.github.io/genai-toolbox/how-to/connect-ide/postgres_mcp/)  
+Connect your IDE to PostgreSQL using Toolbox.
+
 ## Requirements
 
 ### Database User

docs/en/resources/sources/spanner.md

@@ -31,6 +31,11 @@ the Google Cloud console][spanner-quickstart].
 - [`spanner-execute-sql`](../tools/spanner/spanner-execute-sql.md)  
   Run structured and parameterized queries on Spanner.
 
+### Pre-built Configurations
+
+- [Spanner using MCP](https://googleapis.github.io/genai-toolbox/how-to/connect-ide/spanner_mcp/)  
+Connect your IDE to Spanner using Toolbox.
+
 ## Requirements
 
 ### IAM Permissions

docs/en/resources/sources/tidb.md

@@ -0,0 +1,81 @@
+---
+title: "TiDB"
+type: docs
+weight: 1
+description: >
+  TiDB is a distributed SQL database that combines the best of traditional RDBMS and NoSQL databases.
+
+---
+
+## About
+
+[TiDB][tidb-docs] is an open-source distributed SQL database that supports Hybrid Transactional and Analytical Processing (HTAP) workloads. It is MySQL-compatible and features horizontal scalability, strong consistency, and high availability.
+
+[tidb-docs]: https://docs.pingcap.com/tidb/stable
+
+## Requirements
+
+### Database User
+
+This source uses standard MySQL protocol authentication. You will need to [create a TiDB user][tidb-users] to login to the database with.
+
+For TiDB Cloud users, you can create database users through the TiDB Cloud console.
+
+[tidb-users]: https://docs.pingcap.com/tidb/stable/user-account-management
+
+## SSL Configuration
+
+- TiDB Cloud
+
+    For TiDB Cloud instances, SSL is automatically enabled when the hostname matches the TiDB Cloud pattern (`gateway*.*.*.tidbcloud.com`). You don't need to explicitly set `ssl: true` for TiDB Cloud connections.
+
+- Self-Hosted TiDB
+
+    For self-hosted TiDB instances, you can optionally enable SSL by setting `ssl: true` in your configuration.
+
+## Example
+
+- TiDB Cloud
+
+    ```yaml
+    sources:
+        my-tidb-cloud-source:
+            kind: tidb
+            host: gateway01.us-west-2.prod.aws.tidbcloud.com
+            port: 4000
+            database: my_db
+            user: ${TIDB_USERNAME}
+            password: ${TIDB_PASSWORD}
+            # SSL is automatically enabled for TiDB Cloud
+    ```
+
+- Self-Hosted TiDB
+
+    ```yaml
+    sources:
+        my-tidb-source:
+            kind: tidb
+            host: 127.0.0.1
+            port: 4000
+            database: my_db
+            user: ${TIDB_USERNAME}
+            password: ${TIDB_PASSWORD}
+            # ssl: true  # Optional: enable SSL for secure connections
+    ```
+
+{{< notice tip >}}
+Use environment variable replacement with the format ${ENV_NAME}
+instead of hardcoding your secrets into the configuration file.
+{{< /notice >}}
+
+## Reference
+
+| **field** | **type** | **required** | **description**                                                                            |
+|-----------|:--------:|:------------:|--------------------------------------------------------------------------------------------|
+| kind      |  string  |     true     | Must be "tidb".                                                                            |
+| host      |  string  |     true     | IP address or hostname to connect to (e.g. "127.0.0.1" or "gateway01.*.tidbcloud.com").    |
+| port      |  string  |     true     | Port to connect to (typically "4000" for TiDB).                                            |
+| database  |  string  |     true     | Name of the TiDB database to connect to (e.g. "my_db").                                    |
+| user      |  string  |     true     | Name of the TiDB user to connect as (e.g. "my-tidb-user").                                 |
+| password  |  string  |     true     | Password of the TiDB user (e.g. "my-password").                                            |
+| ssl       |  boolean |    false     | Whether to use SSL/TLS encryption. Automatically enabled for TiDB Cloud instances.         |

docs/en/resources/tools/_index.md

@@ -2,8 +2,8 @@
 title: "Tools"
 type: docs
 weight: 2
-description: > 
-  Tools define actions an agent can take -- such as reading and writing to a 
+description: >
+  Tools define actions an agent can take -- such as reading and writing to a
   source.
 ---
 
@@ -114,20 +114,24 @@ in the list using the items field:
 | items       | parameter object |     true     | Specify a Parameter object for the type of the values in the array.         |
 
 {{< notice note >}}
-Items in array should not have a `default` or `required` value. If provided, it will be ignored.
+Items in array should not have a `default` or `required` value. If provided, it
+will be ignored.
 {{< /notice >}}
 
 ### Map Parameters
 
-The map type is a collection of key-value pairs. It can be configured in two ways:
+The map type is a collection of key-value pairs. It can be configured in two
+ways:
 
-- Generic Map: By default, it accepts values of any primitive type (string, integer, float, boolean), allowing for mixed data.
+- Generic Map: By default, it accepts values of any primitive type (string,
+  integer, float, boolean), allowing for mixed data.
 - Typed Map: By setting the valueType field, you can enforce that all values
   within the map must be of the same specified type.
 
 #### Generic Map (Mixed Value Types)
 
-This is the default behavior when valueType is omitted. It's useful for passing a flexible group of settings.
+This is the default behavior when valueType is omitted. It's useful for passing
+a flexible group of settings.
 
 ```yaml
     parameters:
@@ -153,10 +157,10 @@ will be thrown in case of value type mismatch.
 
 Authenticated parameters are automatically populated with user
 information decoded from [ID
-tokens](../authsources/#specifying-id-tokens-from-clients) that are passed in
+tokens](../authServices/#specifying-id-tokens-from-clients) that are passed in
 request headers. They do not take input values in request bodies like other
 parameters. To use authenticated parameters, you must configure the tool to map
-the required [authServices](../authservices) to specific claims within the
+the required [authServices](../authServices/) to specific claims within the
 user's ID token.
 
 ```yaml
@@ -179,7 +183,7 @@ user's ID token.
 
 | **field** | **type** | **required** | **description**                                                                         |
 |-----------|:--------:|:------------:|-----------------------------------------------------------------------------------------|
-| name      |  string  |     true     | Name of the [authServices](../authservices) used to verify the OIDC auth token. |
+| name      |  string  |     true     | Name of the [authServices](../authServices/) used to verify the OIDC auth token.         |
 | field     |  string  |     true     | Claim field decoded from the OIDC token used to auto-populate this parameter.           |
 
 ### Template Parameters
@@ -240,7 +244,7 @@ tools:
 
 You can require an authorization check for any Tool invocation request by
 specifying an `authRequired` field. Specify a list of
-[authServices](../authservices) defined in the previous section.
+[authServices](../authServices/) defined in the previous section.
 
 ```yaml
 tools:

docs/en/resources/tools/alloydbainl/alloydb-ai-nl.md

@@ -2,9 +2,9 @@
 title: "alloydb-ai-nl"
 type: docs
 weight: 1
-description: > 
-  The "alloydb-ai-nl" tool leverages 
-  [AlloyDB AI](https://cloud.google.com/alloydb/ai) next-generation Natural 
+description: >
+  The "alloydb-ai-nl" tool leverages
+  [AlloyDB AI](https://cloud.google.com/alloydb/ai) next-generation Natural
   Language support to provide the ability to query the database directly using
   natural language.
 aliases:
@@ -22,7 +22,7 @@ layer.
 
 This tool is compatible with the following sources:
 
-- [alloydb-postgres](../sources/alloydb-pg.md)
+- [alloydb-postgres](../../sources/alloydb-pg.md)
 
 AlloyDB AI Natural Language delivers secure and accurate responses for
 application end user natural language questions. Natural language streamlines
@@ -69,12 +69,18 @@ database queries.
 You can use the `nlConfigParameters` to list the parameters required for your
 `nl_config`. You **must** supply all parameters required for all PSVs in the
 context. It's strongly recommended to use features like [Authenticated
-Parameters](../tools/#array-parameters) or Bound Parameters to provide secure
+Parameters](../#array-parameters) or Bound Parameters to provide secure
 access to queries generated using natural language, as these parameters are not
 visible to the LLM.
 
 [alloydb-psv]: https://cloud.google.com/alloydb/docs/parameterized-secure-views-overview
 
+{{< notice tip >}} Make sure to enable the `parameterized_views` extension before running this tool. You can do so by running this command in the AlloyDB studio:
+```sql
+CREATE EXTENSION IF NOT EXISTS parameterized_views;
+```
+{{< /notice >}}
+
 ## Example
 
 ```yaml
@@ -88,14 +94,13 @@ tools:
       - name: user_email
         type: string
         description: User ID of the logged in user.
-        # note: we strongly recommend using features like Authenticated or 
-        # Bound parameters to prevent the LLM from seeing these params and 
+        # note: we strongly recommend using features like Authenticated or
+        # Bound parameters to prevent the LLM from seeing these params and
         # specifying values it shouldn't in the tool input
         authServices:
           - name: my_google_service
             field: email
 ```
-
 ## Reference
 
 | **field**          |                  **type**                  | **required** | **description**                                                          |
@@ -104,4 +109,4 @@ tools:
 | source             |                   string                   |     true     | Name of the AlloyDB source the natural language query should execute on. |
 | description        |                   string                   |     true     | Description of the tool that is passed to the LLM.                       |
 | nlConfig           |                   string                   |     true     | The name of the  `nl_config` in AlloyDB                                  |
-| nlConfigParameters | [parameters](_index#specifying-parameters) |     true     | List of PSV parameters defined in the `nl_config`                        |
+| nlConfigParameters | [parameters](../#specifying-parameters) |     true     | List of PSV parameters defined in the `nl_config`                        |

docs/en/resources/tools/bigquery/bigquery-execute-sql.md

@@ -2,7 +2,7 @@
 title: "bigquery-execute-sql"
 type: docs
 weight: 1
-description: > 
+description: >
   A "bigquery-execute-sql" tool executes a SQL statement against BigQuery.
 aliases:
 - /resources/tools/bigquery-execute-sql
@@ -13,10 +13,11 @@ aliases:
 A `bigquery-execute-sql` tool executes a SQL statement against BigQuery.
 It's compatible with the following sources:
 
-- [bigquery](../sources/bigquery.md)
+- [bigquery](../../sources/bigquery.md)
 
-`bigquery-execute-sql` takes one input parameter `sql` and runs the sql
-statement against the `source`.
+`bigquery-execute-sql` takes a required `sql` input parameter and runs the SQL
+statement against the configured `source`. It also supports an optional `dry_run`
+parameter to validate a query without executing it.
 
 ## Example
 

docs/en/resources/tools/bigquery/bigquery-get-dataset-info.md

@@ -2,7 +2,7 @@
 title: "bigquery-get-dataset-info"
 type: docs
 weight: 1
-description: > 
+description: >
   A "bigquery-get-dataset-info" tool retrieves metadata for a BigQuery dataset.
 aliases:
 - /resources/tools/bigquery-get-dataset-info
@@ -13,10 +13,10 @@ aliases:
 A `bigquery-get-dataset-info` tool retrieves metadata for a BigQuery dataset.
 It's compatible with the following sources:
 
-- [bigquery](../sources/bigquery.md)
+- [bigquery](../../sources/bigquery.md)
 
 `bigquery-get-dataset-info` takes a `dataset` parameter to specify the dataset
-on the given source. It also optionally accepts a `project` parameter to 
+on the given source. It also optionally accepts a `project` parameter to
 define the Google Cloud project ID. If the `project` parameter is not provided,
 the tool defaults to using the project defined in the source configuration.
 

docs/en/resources/tools/bigquery/bigquery-get-table-info.md

@@ -2,7 +2,7 @@
 title: "bigquery-get-table-info"
 type: docs
 weight: 1
-description: > 
+description: >
   A "bigquery-get-table-info" tool retrieves metadata for a BigQuery table.
 aliases:
 - /resources/tools/bigquery-get-table-info
@@ -13,11 +13,11 @@ aliases:
 A `bigquery-get-table-info` tool retrieves metadata for a BigQuery table.
 It's compatible with the following sources:
 
-- [bigquery](../sources/bigquery.md)
+- [bigquery](../../sources/bigquery.md)
 
 `bigquery-get-table-info` takes `dataset` and `table` parameters to specify
-the target table. It also optionally accepts a `project` parameter to define 
-the Google Cloud project ID. If the `project` parameter is not provided, the 
+the target table. It also optionally accepts a `project` parameter to define
+the Google Cloud project ID. If the `project` parameter is not provided, the
 tool defaults to using the project defined in the source configuration.
 
 ## Example

docs/en/resources/tools/bigquery/bigquery-list-dataset-ids.md

@@ -2,7 +2,7 @@
 title: "bigquery-list-dataset-ids"
 type: docs
 weight: 1
-description: > 
+description: >
   A "bigquery-list-dataset-ids" tool returns all dataset IDs from the source.
 aliases:
 - /resources/tools/bigquery-list-dataset-ids
@@ -13,10 +13,10 @@ aliases:
 A `bigquery-list-dataset-ids` tool returns all dataset IDs from the source.
 It's compatible with the following sources:
 
-- [bigquery](../sources/bigquery.md)
+- [bigquery](../../sources/bigquery.md)
 
-`bigquery-list-dataset-ids` optionally accepts a `project` parameter to define 
-the Google Cloud project ID. If the `project` parameter is not provided, the 
+`bigquery-list-dataset-ids` optionally accepts a `project` parameter to define
+the Google Cloud project ID. If the `project` parameter is not provided, the
 tool defaults to using the project defined in the source configuration.
 
 ## Example

docs/en/resources/tools/bigquery/bigquery-list-table-ids.md

@@ -2,7 +2,7 @@
 title: "bigquery-list-table-ids"
 type: docs
 weight: 1
-description: > 
+description: >
   A "bigquery-list-table-ids" tool returns table IDs in a given BigQuery dataset.
 aliases:
 - /resources/tools/bigquery-list-table-ids
@@ -13,11 +13,11 @@ aliases:
 A `bigquery-list-table-ids` tool returns table IDs in a given BigQuery dataset.
 It's compatible with the following sources:
 
-- [bigquery](../sources/bigquery.md)
+- [bigquery](../../sources/bigquery.md)
 
 `bigquery-get-dataset-info` takes a required `dataset` parameter to specify the dataset
-from which to list table IDs. It also optionally accepts a `project` parameter to 
-define the Google Cloud project ID. If the `project` parameter is not provided, the 
+from which to list table IDs. It also optionally accepts a `project` parameter to
+define the Google Cloud project ID. If the `project` parameter is not provided, the
 tool defaults to using the project defined in the source configuration.
 
 ## Example

docs/en/resources/tools/bigquery/bigquery-sql.md

@@ -13,7 +13,7 @@ aliases:
 A `bigquery-sql` tool executes a pre-defined SQL statement. It's compatible with
 the following sources:
 
-- [bigquery](../sources/bigquery.md)
+- [bigquery](../../sources/bigquery.md)
 
 ### GoogleSQL
 
@@ -72,7 +72,7 @@ tools:
 > including identifiers, column names, and table names. **This makes it more
 > vulnerable to SQL injections**. Using basic parameters only (see above) is
 > recommended for performance and safety reasons. For more details, please check
-> [templateParameters](_index#template-parameters).
+> [templateParameters](../#template-parameters).
 
 ```yaml
 tools:
@@ -101,5 +101,5 @@ tools:
 | source             |                   string                         |     true     | Name of the source the GoogleSQL should execute on.                                                                                        |
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | The GoogleSQL statement to execute.                                                                                                        |
-| parameters         | [parameters](_index#specifying-parameters)       |    false     | List of [parameters](_index#specifying-parameters) that will be inserted into the SQL statement.                                           |
-| templateParameters | [templateParameters](_index#template-parameters) |    false     | List of [templateParameters](_index#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
+| parameters         | [parameters](../#specifying-parameters)       |    false     | List of [parameters](../#specifying-parameters) that will be inserted into the SQL statement.                                           |
+| templateParameters | [templateParameters](../#template-parameters) |    false     | List of [templateParameters](../#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |

docs/en/resources/tools/bigtable/bigtable-sql.md

@@ -2,8 +2,8 @@
 title: "bigtable-sql"
 type: docs
 weight: 1
-description: > 
-  A "bigtable-sql" tool executes a pre-defined SQL statement against a Google 
+description: >
+  A "bigtable-sql" tool executes a pre-defined SQL statement against a Google
   Cloud Bigtable instance.
 aliases:
 - /resources/tools/bigtable-sql
@@ -14,16 +14,20 @@ aliases:
 A `bigtable-sql` tool executes a pre-defined SQL statement against a Bigtable
 instance. It's compatible with any of the following sources:
 
-- [bigtable](../sources/bigtable.md)
+- [bigtable](../../sources/bigtable.md)
 
 ### GoogleSQL
 
 Bigtable supports SQL queries. The integration with Toolbox supports `googlesql`
 dialect, the specified SQL statement is executed as a [data manipulation
-language (DML)][bigtable-googlesql] statements, and specified parameters will inserted according to their name: e.g. `@name`.
+language (DML)][bigtable-googlesql] statements, and specified parameters will
+inserted according to their name: e.g. `@name`.
 
 {{<notice note>}}
-  Bigtable's GoogleSQL support for DML statements might be limited to certain query types. For detailed information on supported DML statements and use cases, refer to the [Bigtable GoogleSQL use cases](https://cloud.google.com/bigtable/docs/googlesql-overview#use-cases).
+  Bigtable's GoogleSQL support for DML statements might be limited to certain
+  query types. For detailed information on supported DML statements and use
+  cases, refer to the [Bigtable GoogleSQL use
+  cases](https://cloud.google.com/bigtable/docs/googlesql-overview#use-cases).
 {{</notice>}}
 
 [bigtable-googlesql]: https://cloud.google.com/bigtable/docs/googlesql-overview
@@ -41,13 +45,13 @@ tools:
     kind: bigtable-sql
     source: my-bigtable-instance
     statement: |
-      SELECT 
-        TO_INT64(cf[ 'id' ]) as id, 
-        CAST(cf[ 'name' ] AS string) as name, 
-      FROM 
-        mytable 
-      WHERE 
-        TO_INT64(cf[ 'id' ]) = @id 
+      SELECT
+        TO_INT64(cf[ 'id' ]) as id,
+        CAST(cf[ 'name' ] AS string) as name,
+      FROM
+        mytable
+      WHERE
+        TO_INT64(cf[ 'id' ]) = @id
         OR CAST(cf[ 'name' ] AS string) = @name;
     description: |
       Use this tool to get information for a specific user.
@@ -73,7 +77,7 @@ tools:
 > including identifiers, column names, and table names. **This makes it more
 > vulnerable to SQL injections**. Using basic parameters only (see above) is
 > recommended for performance and safety reasons. For more details, please check
-> [templateParameters](_index#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -102,8 +106,8 @@ tools:
 | source             |                   string                         |     true     | Name of the source the SQL should execute on.                                                                                              |
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | SQL statement to execute on.                                                                                                               |
-| parameters         | [parameters](_index#specifying-parameters)       |    false     | List of [parameters](_index#specifying-parameters) that will be inserted into the SQL statement.                                           |
-| templateParameters | [templateParameters](_index#template-parameters) |    false     | List of [templateParameters](_index#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
+| parameters         | [parameters](../#specifying-parameters)       |    false     | List of [parameters](../#specifying-parameters) that will be inserted into the SQL statement.                                           |
+| templateParameters | [templateParameters](#template-parameters) |    false     | List of [templateParameters](#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
 
 ## Tips
 

docs/en/resources/tools/couchbase/couchbase-sql.md

@@ -2,7 +2,7 @@
 title: "couchbase-sql"
 type: docs
 weight: 1
-description: > 
+description: >
   A "couchbase-sql" tool executes a pre-defined SQL statement against a Couchbase
   database.
 aliases:
@@ -14,7 +14,7 @@ aliases:
 A `couchbase-sql` tool executes a pre-defined SQL statement against a Couchbase
 database. It's compatible with any of the following sources:
 
-- [couchbase](../sources/couchbase.md)
+- [couchbase](../../sources/couchbase.md)
 
 The specified SQL statement is executed as a parameterized statement, and specified
 parameters will be used according to their name: e.g. `$id`.
@@ -66,7 +66,7 @@ tools:
 > including identifiers, column names, and table names. **This makes it more
 > vulnerable to SQL injections**. Using basic parameters only (see above) is
 > recommended for performance and safety reasons. For more details, please check
-> [templateParameters](_index#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -95,6 +95,6 @@ tools:
 | source             |                   string                         |     true     | Name of the source the SQL query should execute on.                                                                                        |
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | SQL statement to execute                                                                                                                   |
-| parameters         | [parameters](_index#specifying-parameters)       |    false     | List of [parameters](_index#specifying-parameters) that will be used with the SQL statement.                                               |
-| templateParameters | [templateParameters](_index#template-parameters) |    false     | List of [templateParameters](_index#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
+| parameters         | [parameters](../#specifying-parameters)       |    false     | List of [parameters](../#specifying-parameters) that will be used with the SQL statement.                                               |
+| templateParameters | [templateParameters](#template-parameters) |    false     | List of [templateParameters](#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
 | authRequired       |                array[string]                     |    false     | List of auth services that are required to use this tool.                                                                                  |

docs/en/resources/tools/dataplex/dataplex-lookup-entry.md

@@ -0,0 +1,60 @@
+---
+title: "dataplex-lookup-entry"
+type: docs
+weight: 1
+description: > 
+  A "dataplex-lookup-entry" tool returns details of a particular entry in Dataplex Catalog.
+aliases:
+- /resources/tools/dataplex-lookup-entry
+---
+
+## About
+
+A `dataplex-lookup-entry` tool returns details of a particular entry in Dataplex Catalog.
+It's compatible with the following sources:
+
+- [dataplex](../sources/dataplex.md)
+
+`dataplex-lookup-entry` takes a required `name` parameter which contains the project and location to which the request should be attributed in the following form: projects/{project}/locations/{location} and also a required `entry` parameter which is the resource name of the entry in the following form: projects/{project}/locations/{location}/entryGroups/{entryGroup}/entries/{entry}. It also optionally accepts following parameters:
+  - `view` - View to control which parts of an entry the service should return. It takes integer values from 1-4 corresponding to type of view - BASIC, FULL, CUSTOM, ALL
+  - `aspectTypes` - Limits the aspects returned to the provided aspect types in the format `projects/{project}/locations/{location}/aspectTypes/{aspectType}`. It only works for CUSTOM view.
+  - `paths` - Limits the aspects returned to those associated with the provided paths within the Entry. It only works for CUSTOM view.
+
+## Requirements
+
+### IAM Permissions
+
+Dataplex uses [Identity and Access Management (IAM)][iam-overview] to control
+user and group access to Dataplex resources. Toolbox will use your 
+[Application Default Credentials (ADC)][adc] to authorize and authenticate when 
+interacting with [Dataplex][dataplex-docs].
+
+In addition to [setting the ADC for your server][set-adc], you need to ensure
+the IAM identity has been given the correct IAM permissions for the tasks you
+intend to perform. See [Dataplex Universal Catalog IAM permissions][iam-permissions] 
+and [Dataplex Universal Catalog IAM roles][iam-roles] for more information on
+applying IAM permissions and roles to an identity.
+
+[iam-overview]: https://cloud.google.com/dataplex/docs/iam-and-access-control
+[adc]: https://cloud.google.com/docs/authentication#adc
+[set-adc]: https://cloud.google.com/docs/authentication/provide-credentials-adc
+[iam-permissions]: https://cloud.google.com/dataplex/docs/iam-permissions
+[iam-roles]: https://cloud.google.com/dataplex/docs/iam-roles
+
+## Example
+
+```yaml
+tools:
+  lookup_entry:
+    kind: dataplex-lookup-entry
+    source: my-dataplex-source
+    description: Use this tool to retrieve a specific entry in Dataplex Catalog.
+```
+
+## Reference
+
+| **field**   |                  **type**                  | **required** | **description**                                                                                  |
+|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
+| kind        |                   string                   |     true     | Must be "dataplex-lookup-entry".                                                                 |
+| source      |                   string                   |     true     | Name of the source the tool should execute on.                                                   |
+| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |

docs/en/resources/tools/dataplex/dataplex-search-entries.md

@@ -2,7 +2,7 @@
 title: "dataplex-search-entries"
 type: docs
 weight: 1
-description: > 
+description: >
   A "dataplex-search-entries" tool allows to search for entries based on the provided query.
 aliases:
 - /resources/tools/dataplex-search-entries
@@ -10,31 +10,42 @@ aliases:
 
 ## About
 
-A `dataplex-search-entries` tool returns all entries in Dataplex Catalog (e.g. tables, views, models) that matches given user query.
+A `dataplex-search-entries` tool returns all entries in Dataplex Catalog (e.g.
+tables, views, models) that matches given user query.
 It's compatible with the following sources:
 
-- [dataplex](../sources/dataplex.md)
+- [dataplex](../../sources/dataplex.md)
 
-`dataplex-search-entries` takes a required `query` parameter based on which entries are 
-filtered and returned to the user and a required `name` parameter which is constructed using source's project if user does not provide it explicitly and has the following format: projects/{project}/locations/global. It also optionally accepts following parameters:
-  - `pageSize` - Number of results in the search page. Defaults to `5`.
-  - `pageToken` - Page token received from a previous locations.searchEntries call.
-  - `orderBy` - Specifies the ordering of results. Supported values are: relevance (default), last_modified_timestamp, last_modified_timestamp asc
-  - `semanticSearch` - Specifies whether the search should understand the meaning and intent behind the query, rather than just matching keywords. Defaults to `true`.
-  - `scope` - The scope under which the search should be operating. Since this parameter is not exposed to the toolbox user, it defaults to the organization where the project provided in name is located.
+`dataplex-search-entries` takes a required `query` parameter based on which
+entries are filtered and returned to the user and a required `name` parameter
+which is constructed using source's project if user does not provide it
+explicitly and has the following format: projects/{project}/locations/global. It
+also optionally accepts following parameters:
+
+- `pageSize` - Number of results in the search page. Defaults to `5`.
+- `pageToken` - Page token received from a previous locations.searchEntries
+  call.
+- `orderBy` - Specifies the ordering of results. Supported values are: relevance
+  (default), last_modified_timestamp, last_modified_timestamp asc
+- `semanticSearch` - Specifies whether the search should understand the meaning
+  and intent behind the query, rather than just matching keywords. Defaults to
+  `true`.
+- `scope` - The scope under which the search should be operating. Since this
+  parameter is not exposed to the toolbox user, it defaults to the organization
+  where the project provided in name is located.
 
 ## Requirements
 
 ### IAM Permissions
 
 Dataplex uses [Identity and Access Management (IAM)][iam-overview] to control
-user and group access to Dataplex resources. Toolbox will use your 
-[Application Default Credentials (ADC)][adc] to authorize and authenticate when 
+user and group access to Dataplex resources. Toolbox will use your
+[Application Default Credentials (ADC)][adc] to authorize and authenticate when
 interacting with [Dataplex][dataplex-docs].
 
 In addition to [setting the ADC for your server][set-adc], you need to ensure
 the IAM identity has been given the correct IAM permissions for the tasks you
-intend to perform. See [Dataplex Universal Catalog IAM permissions][iam-permissions] 
+intend to perform. See [Dataplex Universal Catalog IAM permissions][iam-permissions]
 and [Dataplex Universal Catalog IAM roles][iam-roles] for more information on
 applying IAM permissions and roles to an identity.
 
@@ -43,6 +54,7 @@ applying IAM permissions and roles to an identity.
 [set-adc]: https://cloud.google.com/docs/authentication/provide-credentials-adc
 [iam-permissions]: https://cloud.google.com/dataplex/docs/iam-permissions
 [iam-roles]: https://cloud.google.com/dataplex/docs/iam-roles
+[dataplex-docs]: https://cloud.google.com/dataplex
 
 ## Example
 
@@ -60,4 +72,4 @@ tools:
 |-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
 | kind        |                   string                   |     true     | Must be "dataplex-search-entries".                                                               |
 | source      |                   string                   |     true     | Name of the source the tool should execute on.                                                   |
-| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |
+| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |

docs/en/resources/tools/dgraph/dgraph-dql.md

@@ -2,7 +2,7 @@
 title: "dgraph-dql"
 type: docs
 weight: 1
-description: > 
+description: >
   A "dgraph-dql" tool executes a pre-defined DQL statement against a Dgraph
   database.
 aliases:
@@ -14,7 +14,7 @@ aliases:
 A `dgraph-dql` tool executes a pre-defined DQL statement against a Dgraph
 database. It's compatible with any of the following sources:
 
-- [dgraph](../sources/dgraph.md)
+- [dgraph](../../sources/dgraph.md)
 
 To run a statement as a query, you need to set the config `isQuery=true`. For
 upserts or mutations, set `isQuery=false`. You can also configure timeout for a
@@ -121,4 +121,4 @@ tools:
 | statement   |                   string                   |     true     | dql statement to execute                                                                     |
 | isQuery     |                  boolean                   |    false     | To run statement as query set true otherwise false                                           |
 | timeout     |                   string                   |    false     | To set timeout for query                                                                     |
-| parameters  | [parameters](_index#specifying-parameters) |    false     | List of [parameters](_index#specifying-parameters) that will be used with the dql statement. |
+| parameters  | [parameters](../#specifying-parameters) |    false     | List of [parameters](../#specifying-parameters) that will be used with the dql statement. |

docs/en/resources/tools/firestore/firestore-delete-documents.md

@@ -2,7 +2,7 @@
 title: "firestore-delete-documents"
 type: docs
 weight: 1
-description: > 
+description: >
   A "firestore-delete-documents" tool deletes multiple documents from Firestore by their paths.
 aliases:
 - /resources/tools/firestore-delete-documents
@@ -10,14 +10,15 @@ aliases:
 
 ## About
 
-A `firestore-delete-documents` tool deletes multiple documents from Firestore by their paths.
+A `firestore-delete-documents` tool deletes multiple documents from Firestore by
+their paths.
 It's compatible with the following sources:
 
-- [firestore](../sources/firestore.md)
+- [firestore](../../sources/firestore.md)
 
-`firestore-delete-documents` takes one input parameter `documentPaths` which is an array of 
-document paths to delete. The tool uses Firestore's BulkWriter for efficient batch deletion
-and returns the success status for each document.
+`firestore-delete-documents` takes one input parameter `documentPaths` which is
+an array of document paths to delete. The tool uses Firestore's BulkWriter for
+efficient batch deletion and returns the success status for each document.
 
 ## Example
 
@@ -31,8 +32,8 @@ tools:
 
 ## Reference
 
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "firestore-delete-documents".                                                            |
-| source      |                   string                   |     true     | Name of the Firestore source to delete documents from.                                           |
-| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |
+| **field**   |     **type**   | **required** | **description**                                          |
+|-------------|:--------------:|:------------:|----------------------------------------------------------|
+| kind        |     string     |     true     | Must be "firestore-delete-documents".                    |
+| source      |     string     |     true     | Name of the Firestore source to delete documents from.   |
+| description |     string     |     true     | Description of the tool that is passed to the LLM.       |

docs/en/resources/tools/firestore/firestore-get-documents.md

@@ -2,7 +2,7 @@
 title: "firestore-get-documents"
 type: docs
 weight: 1
-description: > 
+description: >
   A "firestore-get-documents" tool retrieves multiple documents from Firestore by their paths.
 aliases:
 - /resources/tools/firestore-get-documents
@@ -10,14 +10,15 @@ aliases:
 
 ## About
 
-A `firestore-get-documents` tool retrieves multiple documents from Firestore by their paths.
+A `firestore-get-documents` tool retrieves multiple documents from Firestore by
+their paths.
 It's compatible with the following sources:
 
-- [firestore](../sources/firestore.md)
+- [firestore](../../sources/firestore.md)
 
-`firestore-get-documents` takes one input parameter `documentPaths` which is an array of 
-document paths, and returns the documents' data along with metadata such as existence status,
-creation time, update time, and read time.
+`firestore-get-documents` takes one input parameter `documentPaths` which is an
+array of document paths, and returns the documents' data along with metadata
+such as existence status, creation time, update time, and read time.
 
 ## Example
 
@@ -31,8 +32,8 @@ tools:
 
 ## Reference
 
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "firestore-get-documents".                                                               |
-| source      |                   string                   |     true     | Name of the Firestore source to retrieve documents from.                                         |
-| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |
+| **field**   |    **type**    | **required** | **description**                                            |
+|-------------|:--------------:|:------------:|------------------------------------------------------------|
+| kind        |     string     |     true     | Must be "firestore-get-documents".                         |
+| source      |     string     |     true     | Name of the Firestore source to retrieve documents from.   |
+| description |     string     |     true     | Description of the tool that is passed to the LLM.         |

docs/en/resources/tools/firestore/firestore-get-rules.md

@@ -2,7 +2,7 @@
 title: "firestore-get-rules"
 type: docs
 weight: 1
-description: > 
+description: >
   A "firestore-get-rules" tool retrieves the active Firestore security rules for the current project.
 aliases:
 - /resources/tools/firestore-get-rules
@@ -10,13 +10,15 @@ aliases:
 
 ## About
 
-A `firestore-get-rules` tool retrieves the active [Firestore security rules](https://firebase.google.com/docs/firestore/security/get-started) for the current project.
+A `firestore-get-rules` tool retrieves the active [Firestore security
+rules](https://firebase.google.com/docs/firestore/security/get-started) for the
+current project.
 It's compatible with the following sources:
 
-- [firestore](../sources/firestore.md)
+- [firestore](../../sources/firestore.md)
 
-`firestore-get-rules` takes no input parameters and returns the security rules content along with metadata 
-such as the ruleset name, and timestamps.
+`firestore-get-rules` takes no input parameters and returns the security rules
+content along with metadata such as the ruleset name, and timestamps.
 
 ## Example
 
@@ -30,8 +32,8 @@ tools:
 
 ## Reference
 
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "firestore-get-rules".                                                                  |
-| source      |                   string                   |     true     | Name of the Firestore source to retrieve rules from.                                            |
-| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                              |
+| **field**   |    **type**   | **required** | **description**                                       |
+|-------------|:-------------:|:------------:|-------------------------------------------------------|
+| kind        |     string    |     true     | Must be "firestore-get-rules".                        |
+| source      |     string    |     true     | Name of the Firestore source to retrieve rules from.  |
+| description |     string    |     true     | Description of the tool that is passed to the LLM.    |

docs/en/resources/tools/firestore/firestore-list-collections.md

@@ -2,7 +2,7 @@
 title: "firestore-list-collections"
 type: docs
 weight: 1
-description: > 
+description: >
   A "firestore-list-collections" tool lists collections in Firestore, either at the root level or as subcollections of a document.
 aliases:
 - /resources/tools/firestore-list-collections
@@ -10,10 +10,14 @@ aliases:
 
 ## About
 
-A `firestore-list-collections` tool lists [collections](https://firebase.google.com/docs/firestore/data-model#collections) in Firestore, either at the root level or as [subcollections](https://firebase.google.com/docs/firestore/data-model#subcollections) of a specific document.
+A `firestore-list-collections` tool lists
+[collections](https://firebase.google.com/docs/firestore/data-model#collections)
+in Firestore, either at the root level or as
+[subcollections](https://firebase.google.com/docs/firestore/data-model#subcollections)
+of a specific document.
 It's compatible with the following sources:
 
-- [firestore](../sources/firestore.md)
+- [firestore](../../sources/firestore.md)
 
 `firestore-list-collections` takes an optional `parentPath` parameter to specify a document
 path. If provided, it lists all subcollections of that document. If not provided, it lists
@@ -31,8 +35,8 @@ tools:
 
 ## Reference
 
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "firestore-list-collections".                                                            |
-| source      |                   string                   |     true     | Name of the Firestore source to list collections from.                                           |
-| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |
+| **field**   |      **type**    | **required** | **description**                                        |
+|-------------|:----------------:|:------------:|--------------------------------------------------------|
+| kind        |      string      |     true     | Must be "firestore-list-collections".                  |
+| source      |      string      |     true     | Name of the Firestore source to list collections from. |
+| description |      string      |     true     | Description of the tool that is passed to the LLM.     |

docs/en/resources/tools/firestore/firestore-query-collection.md

@@ -1,6 +1,17 @@
-# firestore-query-collection
+---
+title: "firestore-query-collection"
+type: docs
+weight: 1
+description: > 
+  A "firestore-query-collection" tool allow to query collections in Firestore.
+aliases:
+- /resources/tools/firestore-query-collection
+---
 
-The `firestore-query-collection` tool allows you to query Firestore collections with filters, ordering, and limit capabilities.
+# About
+
+The `firestore-query-collection` tool allows you to query Firestore collections
+with filters, ordering, and limit capabilities.
 
 ## Configuration
 
@@ -10,9 +21,8 @@ To use this tool, you need to configure it in your YAML configuration file:
 sources:
   my-firestore:
     kind: firestore
-    config:
-      project: my-gcp-project
-      database: "(default)"
+    project: my-gcp-project
+    database: "(default)"
 
 tools:
   query_collection:
@@ -23,17 +33,18 @@ tools:
 
 ## Parameters
 
-| Parameter | Type | Required | Default | Description |
-|-----------|------|----------|---------|-------------|
-| `collectionPath` | string | Yes | - | The path to the Firestore collection to query |
-| `filters` | array | No | - | Array of filter objects (as JSON strings) to apply to the query |
-| `orderBy` | string | No | - | JSON string specifying field and direction to order results |
-| `limit` | integer | No | 100 | Maximum number of documents to return |
-| `analyzeQuery` | boolean | No | false | If true, returns query explain metrics including execution statistics |
+| **parameters**   |   **type**   | **required** | **default** | **description**                                                       |
+|------------------|:------------:|:------------:|:-----------:|-----------------------------------------------------------------------|
+| `collectionPath` |    string    |     true     |      -      | The Firestore Rules source code to validate                           |
+| `filters`        |    array     |     false    |      -      | Array of filter objects (as JSON strings) to apply to the query       |
+| `orderBy`        |    string    |     false    |      -      | JSON string specifying field and direction to order results           |
+| `limit`          |    integer   |     false    |     100     | Maximum number of documents to return                                 |
+| `analyzeQuery`   |    boolean   |     false    |    false    | If true, returns query explain metrics including execution statistics |
 
 ### Filter Format
 
-Each filter in the `filters` array should be a JSON string with the following structure:
+Each filter in the `filters` array should be a JSON string with the following
+structure:
 
 ```json
 {
@@ -44,6 +55,7 @@ Each filter in the `filters` array should be a JSON string with the following st
 ```
 
 Supported operators:
+
 - `<` - Less than
 - `<=` - Less than or equal to
 - `>` - Greater than
@@ -56,10 +68,12 @@ Supported operators:
 - `not-in` - Field value is not in the specified array
 
 Value types supported:
+
 - String: `"value": "text"`
 - Number: `"value": 123` or `"value": 45.67`
 - Boolean: `"value": true` or `"value": false`
-- Array: `"value": ["item1", "item2"]` (for `in`, `not-in`, `array-contains-any` operators)
+- Array: `"value": ["item1", "item2"]` (for `in`, `not-in`, `array-contains-any`
+  operators)
 
 ### OrderBy Format
 
@@ -73,6 +87,7 @@ The `orderBy` parameter should be a JSON string with the following structure:
 ```
 
 Direction values:
+
 - `ASCENDING`
 - `DESCENDING`
 
@@ -154,7 +169,8 @@ The tool returns an array of documents, where each document includes:
 
 ### Response with Query Analysis (analyzeQuery = true)
 
-When `analyzeQuery` is set to true, the tool returns a single object containing documents and explain metrics:
+When `analyzeQuery` is set to true, the tool returns a single object containing
+documents and explain metrics:
 
 ```json
 {
@@ -191,6 +207,7 @@ When `analyzeQuery` is set to true, the tool returns a single object containing
 ## Error Handling
 
 The tool will return errors for:
+
 - Invalid collection path
 - Malformed filter JSON
 - Unsupported operators

docs/en/resources/tools/firestore/firestore-validate-rules.md

@@ -10,7 +10,9 @@ aliases:
 
 ## Overview
 
-The `firestore-validate-rules` tool validates Firestore security rules syntax and semantic correctness without deploying them. It provides detailed error reporting with source positions and code snippets.
+The `firestore-validate-rules` tool validates Firestore security rules syntax
+and semantic correctness without deploying them. It provides detailed error
+reporting with source positions and code snippets.
 
 ## Configuration
 
@@ -28,9 +30,9 @@ This tool requires authentication if the source requires authentication.
 
 ## Parameters
 
-| Parameter | Type   | Required | Description |
-|-----------|--------|----------|-------------|
-| source    | string | Yes      | The Firestore Rules source code to validate |
+| **parameters**  |   **type**   | **required** | **description**                              |
+|-----------------|:------------:|:------------:|----------------------------------------------|
+| source          |    string    |     true     | The Firestore Rules source code to validate  |
 
 ## Response
 
@@ -102,6 +104,7 @@ The tool returns a `ValidationResult` object containing:
 ## Error Handling
 
 The tool will return errors for:
+
 - Missing or empty `source` parameter
 - API errors when calling the Firebase Rules service
 - Network connectivity issues
@@ -115,5 +118,7 @@ The tool will return errors for:
 
 ## Related Tools
 
-- [firestore-get-rules]({{< ref "firestore-get-rules" >}}): Retrieve current active rules
-- [firestore-query-collection]({{< ref "firestore-query-collection" >}}): Test rules by querying collections
+- [firestore-get-rules]({{< ref "firestore-get-rules" >}}): Retrieve current
+  active rules
+- [firestore-query-collection]({{< ref "firestore-query-collection" >}}): Test
+  rules by querying collections

docs/en/resources/tools/http/http.md

@@ -2,7 +2,7 @@
 title: "http"
 type: docs
 weight: 1
-description: > 
+description: >
   A "http" tool sends out an HTTP request to an HTTP endpoint.
 aliases:
 - /resources/tools/http
@@ -50,7 +50,7 @@ tools:
         method: GET
         path: /search
         description: Tool to search information from the example API
-    
+
     my-dynamic-path-tool:
         kind: http
         source: my-http-source
@@ -256,8 +256,8 @@ my-http-tool:
 | method       |                   string                   |     true     | The HTTP method to use (e.g., GET, POST, PUT, DELETE).                                                                                                                                                                     |
 | headers      |             map[string]string              |    false     | A map of headers to include in the HTTP request (overrides source headers).                                                                                                                                                |
 | requestBody  |                   string                   |    false     | The request body payload. Use [go template][go-template-doc] with the parameter name as the placeholder (e.g., `{{.id}}` will be replaced with the value of the parameter that has name `id` in the `bodyParams` section). |
-| queryParams  | [parameters](_index#specifying-parameters) |    false     | List of [parameters](_index#specifying-parameters) that will be inserted into the query string.                                                                                                                            |
-| bodyParams   | [parameters](_index#specifying-parameters) |    false     | List of [parameters](_index#specifying-parameters) that will be inserted into the request body payload.                                                                                                                    |
-| headerParams | [parameters](_index#specifying-parameters) |    false     | List of [parameters](_index#specifying-parameters) that will be inserted as the request headers.                                                                                                                           |
+| queryParams  | [parameters](../#specifying-parameters) |    false     | List of [parameters](../#specifying-parameters) that will be inserted into the query string.                                                                                                                            |
+| bodyParams   | [parameters](../#specifying-parameters) |    false     | List of [parameters](../#specifying-parameters) that will be inserted into the request body payload.                                                                                                                    |
+| headerParams | [parameters](../#specifying-parameters) |    false     | List of [parameters](../#specifying-parameters) that will be inserted as the request headers.                                                                                                                           |
 
 [go-template-doc]: <https://pkg.go.dev/text/template#pkg-overview>

docs/en/resources/tools/looker/looker-get-dimensions.md

@@ -16,7 +16,7 @@ in a given mode in the source.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-get-dimensions` accepts two parameters, the `model` and the `explore`.
 

docs/en/resources/tools/looker/looker-get-explores.md

@@ -16,7 +16,7 @@ for a given model from the source.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-get-explores` accepts one parameter, the
 `model` id.

docs/en/resources/tools/looker/looker-get-filters.md

@@ -16,7 +16,7 @@ in a given mode in the source.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-get-filters` accepts two parameters, the `model` and the `explore`.
 

docs/en/resources/tools/looker/looker-get-looks.md

@@ -16,7 +16,7 @@ name or description.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-get-looks` takes four parameters, the `title`, `desc`, `limit`
 and `offset`.

docs/en/resources/tools/looker/looker-get-measures.md

@@ -2,7 +2,7 @@
 title: "looker-get-measures"
 type: docs
 weight: 1
-description: > 
+description: >
   A "looker-get-measures" tool returns all the measures from a given explore
   in a given model in the source.
 aliases:
@@ -16,7 +16,7 @@ in a given mode in the source.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-get-measures` accepts two parameters, the `model` and the `explore`.
 

docs/en/resources/tools/looker/looker-get-models.md

@@ -2,7 +2,7 @@
 title: "looker-get-models"
 type: docs
 weight: 1
-description: > 
+description: >
   A "looker-get-models" tool returns all the models in the source.
 aliases:
 - /resources/tools/looker-get-models
@@ -14,7 +14,7 @@ A `looker-get-models` tool returns all the models the source.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-get-models` accepts no parameters.
 

docs/en/resources/tools/looker/looker-get-parameters.md

@@ -2,7 +2,7 @@
 title: "looker-get-parameters"
 type: docs
 weight: 1
-description: > 
+description: >
   A "looker-get-parameters" tool returns all the parameters from a given explore
   in a given model in the source.
 aliases:
@@ -16,7 +16,7 @@ in a given mode in the source.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-get-parameters` accepts two parameters, the `model` and the `explore`.
 

docs/en/resources/tools/looker/looker-make-look.md

@@ -0,0 +1,65 @@
+---
+title: "looker-make-look"
+type: docs
+weight: 1
+description: >
+  "looker-make-look" generates a Looker look in the users personal folder in
+  Looker
+aliases:
+- /resources/tools/looker-make-look
+---
+
+## About
+
+The `looker-make-look` creates a saved Look in the user's
+Looker personal folder.
+
+It's compatible with the following sources:
+
+- [looker](../../sources/looker.md)
+
+`looker-make-look` takes eight parameters:
+
+1. the `model`
+2. the `explore`
+3. the `fields` list
+4. an optional set of `filters`
+5. an optional set of `pivots`
+6. an optional set of `sorts`
+7. an optional `limit`
+8. an optional `tz`
+9. an optional `vis_config`
+10. the `title`
+11. an optional `description`
+
+## Example
+
+```yaml
+tools:
+    make_look:
+        kind: looker-make-look
+        source: looker-source
+        description: |
+          make_look Tool
+
+          This tool creates a new look in Looker, using the query
+          parameters and the vis_config specified.
+
+          Most of the parameters are the same as the query_url
+          tool. In addition, there is a title and a description
+          that must be provided.
+
+          The newly created look will be created in the user's
+          personal folder in looker. The look name must be unique.
+
+          The result is a json document with a link to the newly
+          created look.
+```
+
+## Reference
+
+| **field**   |                  **type**                  | **required** | **description**                                                                                  |
+|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
+| kind        |                   string                   |     true     | Must be "looker-make-look"                                                                       |
+| source      |                   string                   |     true     | Name of the source the SQL should execute on.                                                    |
+| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |

docs/en/resources/tools/looker/looker-query-sql.md

@@ -16,9 +16,10 @@ semantic model.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-query-sql` takes eight parameters:
+
 1. the `model`
 2. the `explore`
 3. the `fields` list

docs/en/resources/tools/looker/looker-query-url.md

@@ -0,0 +1,363 @@
+---
+title: "looker-query-url"
+type: docs
+weight: 1
+description: >
+  "looker-query-url" generates a url link to a Looker explore.
+aliases:
+- /resources/tools/looker-query-url
+---
+
+## About
+
+The `looker-query-url` generates a url link to an explore in
+Looker so the query can be investigated further.
+
+It's compatible with the following sources:
+
+- [looker](../../sources/looker.md)
+
+`looker-query-url` takes eight parameters:
+
+1. the `model`
+2. the `explore`
+3. the `fields` list
+4. an optional set of `filters`
+5. an optional set of `pivots`
+6. an optional set of `sorts`
+7. an optional `limit`
+8. an optional `tz`
+9. an optional `vis_config`
+
+## Example
+
+```yaml
+tools:
+    query_url:
+        kind: looker-query-url
+        source: looker-source
+        description: |
+          Query URL Tool
+
+          This tool is used to generate the URL of a query in Looker.
+          The user can then explore the query further inside Looker.
+          The tool also returns the query_id and slug. The parameters
+          are the same as the query tool with an additional vis_config
+          parameter.
+
+          The vis_config is optional. If provided, it will be used to
+          control the default visualization for the query. These are
+          some sample vis_config settings.
+
+          A bar chart -
+          {{
+            "defaults_version": 1,
+            "label_density": 25,
+            "legend_position": "center",
+            "limit_displayed_rows": false,
+            "ordering": "none",
+            "plot_size_by_field": false,
+            "point_style": "none",
+            "show_null_labels": false,
+            "show_silhouette": false,
+            "show_totals_labels": false,
+            "show_value_labels": false,
+            "show_view_names": false,
+            "show_x_axis_label": true,
+            "show_x_axis_ticks": true,
+            "show_y_axis_labels": true,
+            "show_y_axis_ticks": true,
+            "stacking": "normal",
+            "totals_color": "#808080",
+            "trellis": "",
+            "type": "looker_bar",
+            "x_axis_gridlines": false,
+            "x_axis_reversed": false,
+            "x_axis_scale": "auto",
+            "x_axis_zoom": true,
+            "y_axis_combined": true,
+            "y_axis_gridlines": true,
+            "y_axis_reversed": false,
+            "y_axis_scale_mode": "linear",
+            "y_axis_tick_density": "default",
+            "y_axis_tick_density_custom": 5,
+            "y_axis_zoom": true
+          }}
+
+          A column chart with an option advanced_vis_config -
+          {{
+            "advanced_vis_config": "{ chart: { type: 'pie', spacingBottom: 50, spacingLeft: 50, spacingRight: 50, spacingTop: 50, }, legend: { enabled: false, }, plotOptions: { pie: { dataLabels: { enabled: true, format: '\u003cb\u003e{key}\u003c/b\u003e\u003cspan style=\"font-weight: normal\"\u003e - {percentage:.2f}%\u003c/span\u003e', }, showInLegend: false, }, }, series: [], }",
+            "colors": [
+              "grey"
+            ],
+            "defaults_version": 1,
+            "hidden_fields": [],
+            "label_density": 25,
+            "legend_position": "center",
+            "limit_displayed_rows": false,
+            "note_display": "below",
+            "note_state": "collapsed",
+            "note_text": "Unsold inventory only",
+            "ordering": "none",
+            "plot_size_by_field": false,
+            "point_style": "none",
+            "series_colors": {},
+            "show_null_labels": false,
+            "show_silhouette": false,
+            "show_totals_labels": false,
+            "show_value_labels": true,
+            "show_view_names": false,
+            "show_x_axis_label": true,
+            "show_x_axis_ticks": true,
+            "show_y_axis_labels": true,
+            "show_y_axis_ticks": true,
+            "stacking": "normal",
+            "totals_color": "#808080",
+            "trellis": "",
+            "type": "looker_column",
+            "x_axis_gridlines": false,
+            "x_axis_reversed": false,
+            "x_axis_scale": "auto",
+            "x_axis_zoom": true,
+            "y_axes": [],
+            "y_axis_combined": true,
+            "y_axis_gridlines": true,
+            "y_axis_reversed": false,
+            "y_axis_scale_mode": "linear",
+            "y_axis_tick_density": "default",
+            "y_axis_tick_density_custom": 5,
+            "y_axis_zoom": true
+          }}
+
+          A line chart -
+          {{
+            "defaults_version": 1,
+            "hidden_pivots": {},
+            "hidden_series": [],
+            "interpolation": "linear",
+            "label_density": 25,
+            "legend_position": "center",
+            "limit_displayed_rows": false,
+            "plot_size_by_field": false,
+            "point_style": "none",
+            "series_types": {},
+            "show_null_points": true,
+            "show_value_labels": false,
+            "show_view_names": false,
+            "show_x_axis_label": true,
+            "show_x_axis_ticks": true,
+            "show_y_axis_labels": true,
+            "show_y_axis_ticks": true,
+            "stacking": "",
+            "trellis": "",
+            "type": "looker_line",
+            "x_axis_gridlines": false,
+            "x_axis_reversed": false,
+            "x_axis_scale": "auto",
+            "y_axis_combined": true,
+            "y_axis_gridlines": true,
+            "y_axis_reversed": false,
+            "y_axis_scale_mode": "linear",
+            "y_axis_tick_density": "default",
+            "y_axis_tick_density_custom": 5
+          }}
+
+          An area chart -
+          {{
+            "defaults_version": 1,
+            "interpolation": "linear",
+            "label_density": 25,
+            "legend_position": "center",
+            "limit_displayed_rows": false,
+            "plot_size_by_field": false,
+            "point_style": "none",
+            "series_types": {},
+            "show_null_points": true,
+            "show_silhouette": false,
+            "show_totals_labels": false,
+            "show_value_labels": false,
+            "show_view_names": false,
+            "show_x_axis_label": true,
+            "show_x_axis_ticks": true,
+            "show_y_axis_labels": true,
+            "show_y_axis_ticks": true,
+            "stacking": "normal",
+            "totals_color": "#808080",
+            "trellis": "",
+            "type": "looker_area",
+            "x_axis_gridlines": false,
+            "x_axis_reversed": false,
+            "x_axis_scale": "auto",
+            "x_axis_zoom": true,
+            "y_axis_combined": true,
+            "y_axis_gridlines": true,
+            "y_axis_reversed": false,
+            "y_axis_scale_mode": "linear",
+            "y_axis_tick_density": "default",
+            "y_axis_tick_density_custom": 5,
+            "y_axis_zoom": true
+          }}
+
+          A scatter plot -
+          {{
+            "cluster_points": false,
+            "custom_quadrant_point_x": 5,
+            "custom_quadrant_point_y": 5,
+            "custom_value_label_column": "",
+            "custom_x_column": "",
+            "custom_y_column": "",
+            "defaults_version": 1,
+            "hidden_fields": [],
+            "hidden_pivots": {},
+            "hidden_points_if_no": [],
+            "hidden_series": [],
+            "interpolation": "linear",
+            "label_density": 25,
+            "legend_position": "center",
+            "limit_displayed_rows": false,
+            "limit_displayed_rows_values": {
+              "first_last": "first",
+              "num_rows": 0,
+              "show_hide": "hide"
+            },
+            "plot_size_by_field": false,
+            "point_style": "circle",
+            "quadrant_properties": {
+              "0": {
+                "color": "",
+                "label": "Quadrant 1"
+              },
+              "1": {
+                "color": "",
+                "label": "Quadrant 2"
+              },
+              "2": {
+                "color": "",
+                "label": "Quadrant 3"
+              },
+              "3": {
+                "color": "",
+                "label": "Quadrant 4"
+              }
+            },
+            "quadrants_enabled": false,
+            "series_labels": {},
+            "series_types": {},
+            "show_null_points": false,
+            "show_value_labels": false,
+            "show_view_names": true,
+            "show_x_axis_label": true,
+            "show_x_axis_ticks": true,
+            "show_y_axis_labels": true,
+            "show_y_axis_ticks": true,
+            "size_by_field": "roi",
+            "stacking": "normal",
+            "swap_axes": true,
+            "trellis": "",
+            "type": "looker_scatter",
+            "x_axis_gridlines": false,
+            "x_axis_reversed": false,
+            "x_axis_scale": "auto",
+            "x_axis_zoom": true,
+            "y_axes": [
+              {
+                "label": "",
+                "orientation": "bottom",
+                "series": [
+                  {
+                    "axisId": "Channel_0 - average_of_roi_first",
+                    "id": "Channel_0 - average_of_roi_first",
+                    "name": "Channel_0"
+                  },
+                  {
+                    "axisId": "Channel_1 - average_of_roi_first",
+                    "id": "Channel_1 - average_of_roi_first",
+                    "name": "Channel_1"
+                  },
+                  {
+                    "axisId": "Channel_2 - average_of_roi_first",
+                    "id": "Channel_2 - average_of_roi_first",
+                    "name": "Channel_2"
+                  },
+                  {
+                    "axisId": "Channel_3 - average_of_roi_first",
+                    "id": "Channel_3 - average_of_roi_first",
+                    "name": "Channel_3"
+                  },
+                  {
+                    "axisId": "Channel_4 - average_of_roi_first",
+                    "id": "Channel_4 - average_of_roi_first",
+                    "name": "Channel_4"
+                  }
+                ],
+                "showLabels": true,
+                "showValues": true,
+                "tickDensity": "custom",
+                "tickDensityCustom": 100,
+                "type": "linear",
+                "unpinAxis": false
+              }
+            ],
+            "y_axis_combined": true,
+            "y_axis_gridlines": true,
+            "y_axis_reversed": false,
+            "y_axis_scale_mode": "linear",
+            "y_axis_tick_density": "default",
+            "y_axis_tick_density_custom": 5,
+            "y_axis_zoom": true
+          }}
+
+          A single value visualization -
+          {{
+            "defaults_version": 1,
+            "show_view_names": false,
+            "type": "looker_single_record"
+          }}
+
+          A Pie chart -
+          {{
+            "defaults_version": 1,
+            "label_density": 25,
+            "label_type": "labPer",
+            "legend_position": "center",
+            "limit_displayed_rows": false,
+            "ordering": "none",
+            "plot_size_by_field": false,
+            "point_style": "none",
+            "series_types": {},
+            "show_null_labels": false,
+            "show_silhouette": false,
+            "show_totals_labels": false,
+            "show_value_labels": false,
+            "show_view_names": false,
+            "show_x_axis_label": true,
+            "show_x_axis_ticks": true,
+            "show_y_axis_labels": true,
+            "show_y_axis_ticks": true,
+            "stacking": "",
+            "totals_color": "#808080",
+            "trellis": "",
+            "type": "looker_pie",
+            "value_labels": "legend",
+            "x_axis_gridlines": false,
+            "x_axis_reversed": false,
+            "x_axis_scale": "auto",
+            "y_axis_combined": true,
+            "y_axis_gridlines": true,
+            "y_axis_reversed": false,
+            "y_axis_scale_mode": "linear",
+            "y_axis_tick_density": "default",
+            "y_axis_tick_density_custom": 5
+          }}
+
+          The result is a JSON object with the id, slug, the url, and
+          the long_url.
+```
+
+## Reference
+
+| **field**   |                  **type**                  | **required** | **description**                                                                                  |
+|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
+| kind        |                   string                   |     true     | Must be "looker-query-url"                                                                       |
+| source      |                   string                   |     true     | Name of the source the SQL should execute on.                                                    |
+| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |

docs/en/resources/tools/looker/looker-query.md

@@ -16,9 +16,10 @@ semantic model.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-query` takes eight parameters:
+
 1. the `model`
 2. the `explore`
 3. the `fields` list

docs/en/resources/tools/looker/looker-run-look.md

@@ -15,7 +15,7 @@ saved Look.
 
 It's compatible with the following sources:
 
-- [looker](../sources/looker.md)
+- [looker](../../sources/looker.md)
 
 `looker-run-look` takes one parameter, the `look_id`.
 

docs/en/resources/tools/mongodb/mongodb-aggregate.md

@@ -10,11 +10,17 @@ aliases:
 
 ## About
 
-The `mongodb-aggregate` tool is the most powerful query tool for MongoDB, allowing you to process data through a multi-stage pipeline. Each stage transforms the documents as they pass through, enabling complex operations like grouping, filtering, reshaping documents, and performing calculations.
+The `mongodb-aggregate` tool is the most powerful query tool for MongoDB,
+allowing you to process data through a multi-stage pipeline. Each stage
+transforms the documents as they pass through, enabling complex operations like
+grouping, filtering, reshaping documents, and performing calculations.
 
-The core of this tool is the `pipelinePayload`, which must be a string containing a **JSON array of pipeline stage documents**. The tool returns a JSON array of documents produced by the final stage of the pipeline.
+The core of this tool is the `pipelinePayload`, which must be a string
+containing a **JSON array of pipeline stage documents**. The tool returns a JSON
+array of documents produced by the final stage of the pipeline.
 
-A `readOnly` flag can be set to `true` as a safety measure to ensure the pipeline does not contain any write stages (like `$out` or `$merge`).
+A `readOnly` flag can be set to `true` as a safety measure to ensure the
+pipeline does not contain any write stages (like `$out` or `$merge`).
 
 This tool is compatible with the following source kind:
 
@@ -22,7 +28,8 @@ This tool is compatible with the following source kind:
 
 ## Example
 
-Here is an example that calculates the average price and total count of products for each category, but only for products with an "active" status.
+Here is an example that calculates the average price and total count of products
+for each category, but only for products with an "active" status.
 
 ```yaml
 tools:

docs/en/resources/tools/mongodb/mongodb-delete-many.md

@@ -10,9 +10,12 @@ aliases:
 
 ## About
 
-The `mongodb-delete-many` tool performs a **bulk destructive operation**, deleting **ALL** documents from a collection that match a specified filter.
+The `mongodb-delete-many` tool performs a **bulk destructive operation**,
+deleting **ALL** documents from a collection that match a specified filter.
 
-The tool returns the total count of documents that were deleted. If the filter does not match any documents (i.e., the deleted count is 0), the tool will return an error.
+The tool returns the total count of documents that were deleted. If the filter
+does not match any documents (i.e., the deleted count is 0), the tool will
+return an error.
 
 This tool is compatible with the following source kind:
 
@@ -22,7 +25,8 @@ This tool is compatible with the following source kind:
 
 ## Example
 
-Here is an example that performs a cleanup task by deleting all products from the `inventory` collection that belong to a discontinued brand.
+Here is an example that performs a cleanup task by deleting all products from
+the `inventory` collection that belong to a discontinued brand.
 
 ```yaml
 tools:

docs/en/resources/tools/mongodb/mongodb-delete-one.md

@@ -10,11 +10,16 @@ aliases:
 
 ## About
 
-The `mongodb-delete-one` tool performs a destructive operation, deleting the **first single document** that matches a specified filter from a MongoDB collection.
+The `mongodb-delete-one` tool performs a destructive operation, deleting the
+**first single document** that matches a specified filter from a MongoDB
+collection.
 
-If the filter matches multiple documents, only the first one found by the database will be deleted. This tool is useful for removing specific entries, such as a user account or a single item from an inventory based on a unique ID.
+If the filter matches multiple documents, only the first one found by the
+database will be deleted. This tool is useful for removing specific entries,
+such as a user account or a single item from an inventory based on a unique ID.
 
-The tool returns the number of documents deleted, which will be either `1` if a document was found and deleted, or `0` if no matching document was found.
+The tool returns the number of documents deleted, which will be either `1` if a
+document was found and deleted, or `0` if no matching document was found.
 
 This tool is compatible with the following source kind:
 
@@ -24,7 +29,8 @@ This tool is compatible with the following source kind:
 
 ## Example
 
-Here is an example that deletes a specific user account from the `users` collection by matching their unique email address. This is a permanent action.
+Here is an example that deletes a specific user account from the `users`
+collection by matching their unique email address. This is a permanent action.
 
 ```yaml
 tools:

docs/en/resources/tools/mongodb/mongodb-find-one.md

@@ -10,9 +10,13 @@ aliases:
 
 ## About
 
-A `mongodb-find-one` tool is used to retrieve the **first single document** that matches a specified filter from a MongoDB collection. If multiple documents match the filter, you can use `sort` options to control which document is returned. Otherwise, the selection is not guaranteed.
+A `mongodb-find-one` tool is used to retrieve the **first single document** that
+matches a specified filter from a MongoDB collection. If multiple documents
+match the filter, you can use `sort` options to control which document is
+returned. Otherwise, the selection is not guaranteed.
 
-The tool returns a single JSON object representing the document, wrapped in a JSON array.
+The tool returns a single JSON object representing the document, wrapped in a
+JSON array.
 
 This tool is compatible with the following source kind:
 
@@ -22,7 +26,9 @@ This tool is compatible with the following source kind:
 
 ## Example
 
-Here's a common use case: finding a specific user by their unique email address and returning their profile information, while excluding sensitive fields like the password hash.
+Here's a common use case: finding a specific user by their unique email address
+and returning their profile information, while excluding sensitive fields like
+the password hash.
 
 ```yaml
 tools:

docs/en/resources/tools/mongodb/mongodb-find.md

@@ -10,7 +10,11 @@ aliases:
 
 ## About
 
-A `mongodb-find` tool is used to query a MongoDB collection and retrieve documents that match a specified filter. It's a flexible tool that allows you to shape the output by selecting specific fields (**projection**), ordering the results (**sorting**), and restricting the number of documents returned (**limiting**).
+A `mongodb-find` tool is used to query a MongoDB collection and retrieve
+documents that match a specified filter. It's a flexible tool that allows you to
+shape the output by selecting specific fields (**projection**), ordering the
+results (**sorting**), and restricting the number of documents returned
+(**limiting**).
 
 The tool returns a JSON array of the documents found.
 
@@ -20,7 +24,9 @@ This tool is compatible with the following source kind:
 
 ## Example
 
-Here's an example that finds up to 10 users from the `customers` collection who live in a specific city. The results are sorted by their last name, and only their first name, last name, and email are returned.
+Here's an example that finds up to 10 users from the `customers` collection who
+live in a specific city. The results are sorted by their last name, and only
+their first name, last name, and email are returned.
 
 ```yaml
 tools:

docs/en/resources/tools/mongodb/mongodb-insert-many.md

@@ -10,9 +10,14 @@ aliases:
 
 ## About
 
-The `mongodb-insert-many` tool inserts **multiple new documents** into a specified MongoDB collection in a single bulk operation. This is highly efficient for adding large amounts of data at once.
+The `mongodb-insert-many` tool inserts **multiple new documents** into a
+specified MongoDB collection in a single bulk operation. This is highly
+efficient for adding large amounts of data at once.
 
-This tool takes one required parameter named `data`. This `data` parameter must be a string containing a **JSON array of document objects**. Upon successful insertion, the tool returns a JSON array containing the unique `_id` of **each** new document that was created.
+This tool takes one required parameter named `data`. This `data` parameter must
+be a string containing a **JSON array of document objects**. Upon successful
+insertion, the tool returns a JSON array containing the unique `_id` of **each**
+new document that was created.
 
 This tool is compatible with the following source kind:
 
@@ -35,7 +40,8 @@ tools:
     canonical: true
 ```
 
-An LLM would call this tool by providing an array of documents as a JSON string in the `data` parameter, like this:
+An LLM would call this tool by providing an array of documents as a JSON string
+in the `data` parameter, like this:
 `tool_code: log_batch_events(data='[{"event": "login", "user": "user1"}, {"event": "click", "user": "user2"}, {"event": "logout", "user": "user1"}]')`
 
 ---

docs/en/resources/tools/mongodb/mongodb-insert-one.md

@@ -10,9 +10,12 @@ aliases:
 
 ## About
 
-The `mongodb-insert-one` tool inserts a **single new document** into a specified MongoDB collection.
+The `mongodb-insert-one` tool inserts a **single new document** into a specified
+MongoDB collection.
 
-This tool takes one required parameter named `data`, which must be a string containing the JSON object you want to insert. Upon successful insertion, the tool returns the unique `_id` of the newly created document.
+This tool takes one required parameter named `data`, which must be a string
+containing the JSON object you want to insert. Upon successful insertion, the
+tool returns the unique `_id` of the newly created document.
 
 This tool is compatible with the following source kind:
 
@@ -20,7 +23,8 @@ This tool is compatible with the following source kind:
 
 ## Example
 
-Here is an example configuration for a tool that adds a new user to a `users` collection.
+Here is an example configuration for a tool that adds a new user to a `users`
+collection.
 
 ```yaml
 tools:
@@ -33,7 +37,8 @@ tools:
     canonical: false
 ```
 
-An LLM would call this tool by providing the document as a JSON string in the `data` parameter, like this:
+An LLM would call this tool by providing the document as a JSON string in the
+`data` parameter, like this:
 `tool_code: create_new_user(data='{"email": "new.user@example.com", "name": "Jane Doe", "status": "active"}')`
 
 ## Reference

docs/en/resources/tools/mongodb/mongodb-update-many.md

@@ -10,9 +10,12 @@ aliases:
 
 ## About
 
-A `mongodb-update-many` tool updates **all** documents within a specified MongoDB collection that match a given filter. It locates the documents using a `filterPayload` and applies the modifications defined in an `updatePayload`.
+A `mongodb-update-many` tool updates **all** documents within a specified
+MongoDB collection that match a given filter. It locates the documents using a
+`filterPayload` and applies the modifications defined in an `updatePayload`.
 
-The tool returns an array of three integers: `[ModifiedCount, UpsertedCount, MatchedCount]`.
+The tool returns an array of three integers: `[ModifiedCount, UpsertedCount,
+MatchedCount]`.
 
 This tool is compatible with the following source kind:
 
@@ -22,7 +25,8 @@ This tool is compatible with the following source kind:
 
 ## Example
 
-Here's an example configuration. This tool applies a discount to all items within a specific category and also marks them as being on sale.
+Here's an example configuration. This tool applies a discount to all items
+within a specific category and also marks them as being on sale.
 
 ```yaml
 tools:

docs/en/resources/tools/mongodb/mongodb-update-one.md

@@ -10,7 +10,10 @@ aliases:
 
 ## About
 
-A `mongodb-update-one` tool updates a single document within a specified MongoDB collection. It locates the document to be updated using a `filterPayload` and applies modifications defined in an `updatePayload`. If the filter matches multiple documents, only the first one found will be updated.
+A `mongodb-update-one` tool updates a single document within a specified MongoDB
+collection. It locates the document to be updated using a `filterPayload` and
+applies modifications defined in an `updatePayload`. If the filter matches
+multiple documents, only the first one found will be updated.
 
 This tool is compatible with the following source kind:
 
@@ -20,7 +23,10 @@ This tool is compatible with the following source kind:
 
 ## Example
 
-Here's an example of a `mongodb-update-one` tool configuration. This tool updates the `stock` and `status` fields of a document in the `inventory` collection where the `item` field matches a provided value. If no matching document is found, the `upsert: true` option will create a new one.
+Here's an example of a `mongodb-update-one` tool configuration. This tool
+updates the `stock` and `status` fields of a document in the `inventory`
+collection where the `item` field matches a provided value. If no matching
+document is found, the `upsert: true` option will create a new one.
 
 ```yaml
 tools:

docs/en/resources/tools/mssql/mssql-execute-sql.md

@@ -2,7 +2,7 @@
 title: "mssql-execute-sql"
 type: docs
 weight: 1
-description: > 
+description: >
   A "mssql-execute-sql" tool executes a SQL statement against a SQL Server
   database.
 aliases:
@@ -14,8 +14,8 @@ aliases:
 A `mssql-execute-sql` tool executes a SQL statement against a SQL Server
 database. It's compatible with any of the following sources:
 
-- [cloud-sql-mssql](../sources/cloud-sql-mssql.md)
-- [mssql](../sources/mssql.md)
+- [cloud-sql-mssql](../../sources/cloud-sql-mssql.md)
+- [mssql](../../sources/mssql.md)
 
 `mssql-execute-sql` takes one input parameter `sql` and run the sql
 statement against the `source`.

docs/en/resources/tools/mssql/mssql-sql.md

@@ -2,7 +2,7 @@
 title: "mssql-sql"
 type: docs
 weight: 1
-description: > 
+description: >
   A "mssql-sql" tool executes a pre-defined SQL statement against a SQL Server
   database.
 aliases:
@@ -14,8 +14,8 @@ aliases:
 A `mssql-sql` tool executes a pre-defined SQL statement against a SQL Server
 database. It's compatible with any of the following sources:
 
-- [cloud-sql-mssql](../sources/cloud-sql-mssql.md)
-- [mssql](../sources/mssql.md)
+- [cloud-sql-mssql](../../sources/cloud-sql-mssql.md)
+- [mssql](../../sources/mssql.md)
 
 Toolbox supports the [prepare statement syntax][prepare-statement] of MS SQL
 Server and expects parameters in the SQL query to be in the form of either
@@ -78,7 +78,7 @@ tools:
 > including identifiers, column names, and table names. **This makes it more
 > vulnerable to SQL injections**. Using basic parameters only (see above) is
 > recommended for performance and safety reasons. For more details, please check
-> [templateParameters](_index#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -107,5 +107,5 @@ tools:
 | source             |                   string                         |     true     | Name of the source the T-SQL statement should execute on.                                                                                  |
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | SQL statement to execute.                                                                                                                  |
-| parameters         | [parameters](_index#specifying-parameters)       |    false     | List of [parameters](_index#specifying-parameters) that will be inserted into the SQL statement.                                           |
-| templateParameters | [templateParameters](_index#template-parameters) |    false     | List of [templateParameters](_index#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
+| parameters         | [parameters](../#specifying-parameters)       |    false     | List of [parameters](../#specifying-parameters) that will be inserted into the SQL statement.                                           |
+| templateParameters | [templateParameters](#template-parameters) |    false     | List of [templateParameters](#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |

docs/en/resources/tools/mysql/mysql-execute-sql.md

@@ -2,7 +2,7 @@
 title: "mysql-execute-sql"
 type: docs
 weight: 1
-description: > 
+description: >
   A "mysql-execute-sql" tool executes a SQL statement against a MySQL
   database.
 aliases:
@@ -14,8 +14,8 @@ aliases:
 A `mysql-execute-sql` tool executes a SQL statement against a MySQL
 database. It's compatible with any of the following sources:
 
-- [cloud-sql-mysql](../sources/cloud-sql-mysql.md)
-- [mysql](../sources/mysql.md)
+- [cloud-sql-mysql](../../sources/cloud-sql-mysql.md)
+- [mysql](../../sources/mysql.md)
 
 `mysql-execute-sql` takes one input parameter `sql` and run the sql
 statement against the `source`.

docs/en/resources/tools/mysql/mysql-sql.md

@@ -2,7 +2,7 @@
 title: "mysql-sql"
 type: docs
 weight: 1
-description: > 
+description: >
   A "mysql-sql" tool executes a pre-defined SQL statement against a MySQL
   database.
 aliases:
@@ -14,8 +14,8 @@ aliases:
 A `mysql-sql` tool executes a pre-defined SQL statement against a MySQL
 database. It's compatible with any of the following sources:
 
-- [cloud-sql-mysql](../sources/cloud-sql-mysql.md)
-- [mysql](../sources/mysql.md)
+- [cloud-sql-mysql](../../sources/cloud-sql-mysql.md)
+- [mysql](../../sources/mysql.md)
 
 The specified SQL statement is executed as a [prepared statement][mysql-prepare],
 and expects parameters in the SQL query to be in the form of placeholders `?`.
@@ -73,7 +73,7 @@ tools:
 > including identifiers, column names, and table names. **This makes it more
 > vulnerable to SQL injections**. Using basic parameters only (see above) is
 > recommended for performance and safety reasons. For more details, please check
-> [templateParameters](_index#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -102,5 +102,5 @@ tools:
 | source             |                   string                         |     true     | Name of the source the SQL should execute on.                                                                                              |
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | SQL statement to execute on.                                                                                                               |
-| parameters         | [parameters](_index#specifying-parameters)       |    false     | List of [parameters](_index#specifying-parameters) that will be inserted into the SQL statement.                                           |
-| templateParameters | [templateParameters](_index#template-parameters) |    false     | List of [templateParameters](_index#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
+| parameters         | [parameters](../#specifying-parameters)       |    false     | List of [parameters](../#specifying-parameters) that will be inserted into the SQL statement.                                           |
+| templateParameters | [templateParameters](#template-parameters) |    false     | List of [templateParameters](#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |

docs/en/resources/tools/neo4j/neo4j-cypher.md

@@ -2,7 +2,7 @@
 title: "neo4j-cypher"
 type: docs
 weight: 1
-description: > 
+description: >
   A "neo4j-cypher" tool executes a pre-defined cypher statement against a Neo4j
   database.
 aliases:
@@ -14,7 +14,7 @@ aliases:
 A `neo4j-cypher` tool executes a pre-defined Cypher statement against a Neo4j
 database. It's compatible with any of the following sources:
 
-- [neo4j](../sources/neo4j.md)
+- [neo4j](../../sources/neo4j.md)
 
 The specified Cypher statement is executed as a [parameterized
 statement][neo4j-parameters], and specified parameters will be used according to
@@ -63,7 +63,7 @@ tools:
         description: Full actor name, "firstname lastname"
       - name: year
         type: integer
-        description: 4 digit number starting in 1900 up to the current year 
+        description: 4 digit number starting in 1900 up to the current year
 ```
 
 ## Reference
@@ -74,4 +74,4 @@ tools:
 | source      |                   string                   |     true     | Name of the source the Cypher query should execute on.                                          |
 | description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                              |
 | statement   |                   string                   |     true     | Cypher statement to execute                                                                     |
-| parameters  | [parameters](_index#specifying-parameters) |    false     | List of [parameters](_index#specifying-parameters) that will be used with the Cypher statement. |
+| parameters  | [parameters](../#specifying-parameters) |    false     | List of [parameters](../#specifying-parameters) that will be used with the Cypher statement. |

docs/en/resources/tools/neo4j/neo4j-execute-cypher.md

@@ -2,7 +2,7 @@
 title: "neo4j-execute-cypher"
 type: docs
 weight: 1
-description: > 
+description: >
   A "neo4j-execute-cypher" tool executes any arbitrary Cypher statement against a Neo4j
   database.
 aliases:
@@ -11,15 +11,24 @@ aliases:
 
 ## About
 
-A `neo4j-execute-cypher` tool executes an arbitrary Cypher query provided as a string parameter against a Neo4j database. It's designed to be a flexible tool for interacting with the database when a pre-defined query is not sufficient. This tool is compatible with any of the following sources:
+A `neo4j-execute-cypher` tool executes an arbitrary Cypher query provided as a
+string parameter against a Neo4j database. It's designed to be a flexible tool
+for interacting with the database when a pre-defined query is not sufficient.
+This tool is compatible with any of the following sources:
 
-- [neo4j](../sources/neo4j.md)
+- [neo4j](../../sources/neo4j.md)
 
-For security, the tool can be configured to be read-only. If the `readOnly` flag is set to `true`, the tool will analyze the incoming Cypher query and reject any write operations (like `CREATE`, `MERGE`, `DELETE`, etc.) before execution.
+For security, the tool can be configured to be read-only. If the `readOnly` flag
+is set to `true`, the tool will analyze the incoming Cypher query and reject any
+write operations (like `CREATE`, `MERGE`, `DELETE`, etc.) before execution.
 
-The Cypher query uses standard [Neo4j Cypher](https://neo4j.com/docs/cypher-manual/current/queries/) syntax and supports all Cypher features, including pattern matching, filtering, and aggregation.
+The Cypher query uses standard [Neo4j
+Cypher](https://neo4j.com/docs/cypher-manual/current/queries/) syntax and
+supports all Cypher features, including pattern matching, filtering, and
+aggregation.
 
-`neo4j-execute-cypher` takes one input parameter `cypher` and run the cypher query against the `source`.
+`neo4j-execute-cypher` takes one input parameter `cypher` and run the cypher
+query against the `source`.
 
 > **Note:** This tool is intended for developer assistant workflows with
 > human-in-the-loop and shouldn't be used for production agents.
@@ -50,4 +59,3 @@ tools:
 | source      |                   string                   |     true     | Name of the source the Cypher query should execute on.                                          |
 | description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                              |
 | readOnly    |                   boolean                  |     false    | If set to `true`, the tool will reject any write operations in the Cypher query. Default is `false`. |
-