adjust UI design to use icons and better match style

.ci/integration.cloudbuild.yaml

@@ -444,27 +444,6 @@ steps:
           valkey \
           valkey
 
-  - id: "oceanbase"
-    name: golang:1
-    waitFor: ["compile-test-binary"]
-    entrypoint: /bin/bash
-    env:
-      - "GOPATH=/gopath"
-      - "OCEANBASE_PORT=$_OCEANBASE_PORT"
-      - "OCEANBASE_DATABASE=$_OCEANBASE_DATABASE"
-      - "SERVICE_ACCOUNT_EMAIL=$SERVICE_ACCOUNT_EMAIL"
-    secretEnv: ["CLIENT_ID", "OCEANBASE_HOST", "OCEANBASE_USER", "OCEANBASE_PASSWORD"]
-    volumes:
-      - name: "go"
-        path: "/gopath"
-    args:
-      - -c
-      - |
-        .ci/test_with_coverage.sh \
-          "OceanBase" \
-          oceanbase \
-          oceanbase
-          
   - id: "firestore"
     name: golang:1
     waitFor: ["compile-test-binary"]
@@ -553,51 +532,6 @@ steps:
           tidb \
           tidbsql tidbexecutesql
 
-  - id: "firebird"
-    name: golang:1
-    waitFor: ["compile-test-binary"]
-    entrypoint: /bin/bash
-    env:
-      - "GOPATH=/gopath"
-      - "FIREBIRD_DATABASE=$_FIREBIRD_DATABASE_NAME"
-      - "FIREBIRD_HOST=$_FIREBIRD_HOST"
-      - "FIREBIRD_PORT=$_FIREBIRD_PORT"
-      - "SERVICE_ACCOUNT_EMAIL=$SERVICE_ACCOUNT_EMAIL"
-    secretEnv: ["CLIENT_ID", "FIREBIRD_USER", "FIREBIRD_PASS"]
-    volumes:
-      - name: "go"
-        path: "/gopath"
-    args:
-      - -c
-      - |
-        .ci/test_with_coverage.sh \
-          "Firebird" \
-          firebird \
-          firebirdsql firebirdexecutesql
-
-  - id: "trino"
-    name: golang:1
-    waitFor: ["compile-test-binary"]
-    entrypoint: /bin/bash
-    env:
-      - "GOPATH=/gopath"
-      - "TRINO_HOST=$_TRINO_HOST"
-      - "TRINO_PORT=$_TRINO_PORT"
-      - "TRINO_CATALOG=$_TRINO_CATALOG"
-      - "TRINO_SCHEMA=$_TRINO_SCHEMA"
-      - "SERVICE_ACCOUNT_EMAIL=$SERVICE_ACCOUNT_EMAIL"
-    secretEnv: ["CLIENT_ID", "TRINO_USER"]
-    volumes:
-      - name: "go"
-        path: "/gopath"
-    args:
-      - -c
-      - |
-        .ci/test_with_coverage.sh \
-          "Trino" \
-          trino \
-          trinosql trinoexecutesql
-
 availableSecrets:
   secretManager:
     - versionName: projects/$PROJECT_ID/secrets/cloud_sql_pg_user/versions/latest
@@ -650,28 +584,16 @@ availableSecrets:
       env: REDIS_PASS
     - versionName: projects/$PROJECT_ID/secrets/memorystore_valkey_address/versions/latest
       env: VALKEY_ADDRESS
-    - versionName: projects/$PROJECT_ID/secrets/looker_base_url/versions/latest
+    - versionName: projects/107716898620/secrets/looker_base_url/versions/latest
       env: LOOKER_BASE_URL
-    - versionName: projects/$PROJECT_ID/secrets/looker_client_id/versions/latest
+    - versionName: projects/107716898620/secrets/looker_client_id/versions/latest
       env: LOOKER_CLIENT_ID
-    - versionName: projects/$PROJECT_ID/secrets/looker_client_secret/versions/latest
+    - versionName: projects/107716898620/secrets/looker_client_secret/versions/latest
       env: LOOKER_CLIENT_SECRET
-    - versionName: projects/$PROJECT_ID/secrets/tidb_user/versions/latest
+    - versionName: projects/107716898620/secrets/tidb_user/versions/latest
       env: TIDB_USER
-    - versionName: projects/$PROJECT_ID/secrets/tidb_pass/versions/latest
+    - versionName: projects/107716898620/secrets/tidb_pass/versions/latest
       env: TIDB_PASS
-    - versionName: projects/$PROJECT_ID/secrets/firebird_user/versions/latest
-      env: FIREBIRD_USER
-    - versionName: projects/$PROJECT_ID/secrets/firebird_pass/versions/latest
-      env: FIREBIRD_PASS
-    - versionName: projects/$PROJECT_ID/secrets/trino_user/versions/latest
-      env: TRINO_USER
-    - versionName: projects/$PROJECT_ID/secrets/oceanbase_host/versions/latest
-      env: OCEANBASE_HOST
-    - versionName: projects/$PROJECT_ID/secrets/oceanbase_user/versions/latest
-      env: OCEANBASE_USER
-    - versionName: projects/$PROJECT_ID/secrets/oceanbase_pass/versions/latest
-      env: OCEANBASE_PASSWORD
 
 options:
   logging: CLOUD_LOGGING_ONLY
@@ -683,7 +605,6 @@ options:
 
 substitutions:
   _DATABASE_NAME: test_database
-  _FIREBIRD_DATABASE_NAME: /firebird/test_database.fdb
   _REGION: "us-central1"
   _CLOUD_SQL_POSTGRES_INSTANCE: "cloud-sql-pg-testing"
   _ALLOYDB_POSTGRES_CLUSTER: "alloydb-pg-testing"
@@ -707,11 +628,3 @@ substitutions:
   _LOOKER_VERIFY_SSL: "true"
   _TIDB_HOST: 127.0.0.1
   _TIDB_PORT: "4000"
-  _FIREBIRD_HOST: 127.0.0.1
-  _FIREBIRD_PORT: "3050"
-  _TRINO_HOST: 127.0.0.1
-  _TRINO_PORT: "8080"
-  _TRINO_CATALOG: "memory"
-  _TRINO_SCHEMA: "default"
-  _OCEANBASE_PORT: "2883"
-  _OCEANBASE_DATABASE: "oceanbase"

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,21 +0,0 @@
-## Description
----
-> Should include a concise description of the changes (bug or feature), it's
-> impact, along with a summary of the solution
-
-## PR Checklist
----
-> Thank you for opening a Pull Request! Before submitting your PR, there are a
-> few things you can do to make sure it goes smoothly:
-- [ ] Make sure you reviewed
-  [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
-- [ ] Make sure to open an issue as a
-  [bug/issue](https://github.com/googleapis/langchain-google-alloydb-pg-python/issues/new/choose)
-  before writing your code!  That way we can discuss the change, evaluate
-  designs, and agree on the general idea
-- [ ] Ensure the tests and linter pass
-- [ ] Code coverage does not decrease (if any source code was changed)
-- [ ] Appropriate docs were updated (if necessary)
-- [ ] Make sure to add `!` if this involve a breaking change
-
-🛠️ Fixes #<issue_number_goes_here>

.github/blunderbuss.yml

@@ -9,10 +9,6 @@ assign_issues_by:
     - Genesis929
     - shobsi
     - jiaxunwu
-  - labels:
-    - 'product: looker'
-    to:
-    - drstrangelooker
 assign_prs:
   - Yuan325
   - duwenxin99

.github/labels.yaml

@@ -84,15 +84,7 @@
   color: 8befd7
   description: 'Status: waiting for feedback from community or issue author.'
 
-- name: 'status: waiting for response'
-  color: 8befd7
-  description: 'Status: reviewer is awaiting feedback or responses from the author before proceeding.'
-
 # Product Labels
 - name: 'product: bigquery'
   color: 5065c7
   description: 'Product: Assigned to the BigQuery team.'
-# Product Labels
-- name: 'product: looker'
-  color: 5065c7
-  description: 'Product: Assigned to the Looker team.'

.github/release-please.yml

@@ -38,8 +38,6 @@ 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

@@ -39,7 +39,7 @@ jobs:
       group: ${{ github.workflow }}-${{ github.ref }}
       cancel-in-progress: true
     steps:
-      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
         with:
           fetch-depth: 0 # Fetch all history for .GitInfo and .Lastmod
 
@@ -55,7 +55,7 @@ jobs:
           node-version: "22"
 
       - name: Cache dependencies
-        uses: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809 # v4
+        uses: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684 # v4
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}

.github/workflows/docs_preview_clean.yaml

@@ -34,7 +34,7 @@ jobs:
       group: "preview-${{ github.event.number }}"
       cancel-in-progress: true
     steps:
-      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
         with:
           ref: gh-pages
 

.github/workflows/docs_preview_deploy.yaml

@@ -49,7 +49,7 @@ jobs:
       group: "preview-${{ github.event.number }}"
       cancel-in-progress: true
     steps:
-      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
         with:
           # Checkout the PR's HEAD commit (supports forks).
           ref: ${{ github.event.pull_request.head.sha }}
@@ -67,7 +67,7 @@ jobs:
           node-version: "22"
 
       - name: Cache dependencies
-        uses: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809 # v4
+        uses: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684 # v4
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}

.github/workflows/lint.yaml

@@ -55,7 +55,7 @@ jobs:
         with:
           go-version: "1.22"
       - name: Checkout code
-        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ github.event.pull_request.head.sha }}
           repository: ${{ github.event.pull_request.head.repo.full_name }}

.github/workflows/sync-labels.yaml

@@ -29,7 +29,7 @@ jobs:
       issues: 'write'
       pull-requests: 'write'
     steps:
-      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
       - uses: micnncim/action-label-syncer@3abd5ab72fda571e69fffd97bd4e0033dd5f495c # v1.3.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/tests.yaml

@@ -16,7 +16,7 @@ name: tests
 on:
   push:
     branches:
-      - "main"
+    - 'main'
   pull_request:
   pull_request_target:
     types: [labeled]
@@ -35,9 +35,9 @@ jobs:
         os: [macos-latest, windows-latest, ubuntu-latest]
       fail-fast: false
     permissions:
-      contents: "read"
-      issues: "write"
-      pull-requests: "write"
+      contents: 'read'
+      issues: 'write'
+      pull-requests: 'write'
     steps:
       - name: Remove PR label
         if: "${{ github.event.action == 'labeled' && github.event.label.name == 'tests: run' }}"
@@ -62,7 +62,7 @@ jobs:
           go-version: "1.22"
 
       - name: Checkout code
-        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ github.event.pull_request.head.sha }}
           repository: ${{ github.event.pull_request.head.repo.full_name }}
@@ -76,8 +76,6 @@ jobs:
 
       - name: Run tests with coverage
         if: ${{ runner.os == 'Linux' }}
-        env:
-          GOTOOLCHAIN: go1.25.0+auto
         run: |
           source_dir="./internal/sources/*"
           tool_dir="./internal/tools/*"

.gitignore

@@ -20,4 +20,4 @@ node_modules
 
 # executable
 genai-toolbox
-toolbox
+toolbox

.hugo/hugo.toml

@@ -8,8 +8,6 @@ defaultContentLanguageInSubdir = false
 enableGitInfo = true
 enableRobotsTXT = true
 
-ignoreFiles = ["quickstart/shared", "quickstart/python", "quickstart/js", "quickstart/go"]
-
 [languages]
   [languages.en]
     languageName ="English"

.hugo/layouts/shortcodes/ipynb.html

@@ -1,47 +0,0 @@
-{{ $notebookFile := .Get 0 }}
-{{ with .Page.Resources.Get $notebookFile }}
-
-  {{ $content := .Content | transform.Unmarshal }}
-  {{ range $content.cells }}
-
-    {{ if eq .cell_type "markdown" }}
-      <div class="notebook-markdown">
-        {{ $markdown := "" }}
-        {{ range .source }}{{ $markdown = print $markdown . }}{{ end }}
-        {{ $markdown | markdownify }}
-      </div>
-    {{ end }}
-
-    {{ if eq .cell_type "code" }}
-      <div class="notebook-code">
-        {{ $code := "" }}
-        {{ range .source }}{{ $code = print $code . }}{{ end }}
-        {{ highlight $code "python" "" }}
-
-        {{ range .outputs }}
-          <div class="notebook-output">
-            {{ with .text }}
-              <pre class="notebook-stream"><code>{{- range . }}{{ . }}{{ end -}}</code></pre>
-            {{ end }}
-
-            {{ with .data }}
-              {{ with index . "image/png" }}
-                <img src="data:image/png;base64,{{ . }}" alt="Notebook output image">
-              {{ end }}
-              {{ with index . "image/jpeg" }}
-                <img src="data:image/jpeg;base64,{{ . }}" alt="Notebook output image">
-              {{ end }}
-              {{ with index . "text/html" }}
-                {{ $html := "" }}
-                {{ range . }}{{ $html = print $html . }}{{ end }}
-                {{ $html | safeHTML }}
-              {{ end }}
-            {{ end }}
-          </div>
-        {{ end }}
-      </div>
-    {{ end }}
-  {{ end }}
-{{ else }}
-  <p style="color: red;">Error: Notebook '{{ $notebookFile }}' not found in page resources.</p>
-{{ end }}

.hugo/layouts/shortcodes/regionInclude.html

@@ -1,49 +0,0 @@
-{{/*
-  snippet.html
-  Usage:
-    {{< regionInclude "filename.md" "region_name" >}}
-    {{< regionInclude "filename.python" "region_name" "python" >}}
-*/}}
-
-{{ $file := .Get 0 }}
-{{ $region := .Get 1 }}
-{{ $lang := .Get 2 | default "text" }}
-{{ $path := printf "%s%s" .Page.File.Dir $file }}
-
-{{ if or (not $file) (eq $file "") }}
-  {{ errorf "The file parameter (first argument) is required and must be non-empty in %s" .Page.File.Path }}
-{{ end }}
-{{ if or (not $region) (eq $region "") }}
-  {{ errorf "The region parameter (second argument) is required and must be non-empty in %s" .Page.File.Path }}
-{{ end }}
-{{ if not (fileExists $path) }}
-  {{ errorf "File %q not found (referenced in %s)" $path .Page.File.Path }}
-{{ end }}
-
-{{ $content := readFile $path }}
-{{ $start_tag := printf "[START %s]" $region }}
-{{ $end_tag := printf "[END %s]" $region }}
-
-{{ $snippet := "" }}
-{{ $in_snippet := false }}
-{{ range split $content "\n" }}
-  {{ if $in_snippet }}
-    {{ if in . $end_tag }}
-      {{ $in_snippet = false }}
-    {{ else }}
-      {{ $snippet = printf "%s%s\n" $snippet . }}
-    {{ end }}
-  {{ else if in . $start_tag }}
-    {{ $in_snippet = true }}
-  {{ end }}
-{{ end }}
-
-{{ if eq (trim $snippet "") "" }}
-  {{ errorf "Region %q not found or empty in file %s (referenced in %s)" $region $file .Page.File.Path }}
-{{ end }}
-
-{{ if eq $lang "text" }}
-  {{ $snippet | markdownify }}
-{{ else }}
-  {{ highlight (trim $snippet "\n") $lang "" }}
-{{ end }}

CHANGELOG.md

@@ -1,30 +1,5 @@
 # Changelog
 
-## [0.12.0](https://github.com/googleapis/genai-toolbox/compare/v0.11.0...v0.12.0) (2025-08-14)
-
-
-### Features
-
-* **prebuiltconfig:** Introduce additional parameter to limit context in list_tables ([#1151](https://github.com/googleapis/genai-toolbox/issues/1151)) ([497d3b1](https://github.com/googleapis/genai-toolbox/commit/497d3b126da252a4b59806ca2ca3c56e78efc13d))
-* **prebuiltconfig/alloydb-admin:** Add list cluster, instance and users ([#1126](https://github.com/googleapis/genai-toolbox/issues/1126)) ([b42c139](https://github.com/googleapis/genai-toolbox/commit/b42c139158650fb1f3b696965e840c52e2016bf0))
-* **prebuiltconfig/alloydb-admin:** Add tool to create user via Built in user type or IAM ([#1130](https://github.com/googleapis/genai-toolbox/issues/1130)) ([f5bcb9c](https://github.com/googleapis/genai-toolbox/commit/f5bcb9c755a2c1747d0beeda568b6217d7420e7a))
-* **source/http:** Add User Agent to `http` invocations ([#1102](https://github.com/googleapis/genai-toolbox/issues/1102)) ([6f55b78](https://github.com/googleapis/genai-toolbox/commit/6f55b78e96b8c7aa9aca601cfae4d62f3e1eb42b))
-* **sources/postgres:** Add support for `queryParams` ([#1047](https://github.com/googleapis/genai-toolbox/issues/1047)) ([7b57251](https://github.com/googleapis/genai-toolbox/commit/7b5725140279de21fece45e860945b7a7d23e7d0)), closes [#963](https://github.com/googleapis/genai-toolbox/issues/963)
-* **tools/bigquery-execute-sql:** Add dry run support ([#1057](https://github.com/googleapis/genai-toolbox/issues/1057)) ([1cac9b5](https://github.com/googleapis/genai-toolbox/commit/1cac9b5b378153c7dc65ff3dfb4ebd852b715a10))
-* **tools/dataplex-search-aspect-types:** Add support for `dataplex-search-aspect-types` tool ([#1061](https://github.com/googleapis/genai-toolbox/issues/1061)) ([d940187](https://github.com/googleapis/genai-toolbox/commit/d940187c851666cc201f519665fb4f2e1478465c))
-* **tools/looker:** Add `looker-make-look` tool to create Looks ([#1099](https://github.com/googleapis/genai-toolbox/issues/1099)) ([61d9489](https://github.com/googleapis/genai-toolbox/commit/61d94893448f633a5f2b9d7f0744ab40704af824))
-* **tools/looker:** Add visualizations to `query-url` tool ([#1090](https://github.com/googleapis/genai-toolbox/issues/1090)) ([5bf2758](https://github.com/googleapis/genai-toolbox/commit/5bf275846a268a8d305d6392fa4e8e79e365f00d))
-* **tools/looker:** New Looker tools for dashboards ([#1118](https://github.com/googleapis/genai-toolbox/issues/1118)) ([42be3f5](https://github.com/googleapis/genai-toolbox/commit/42be3f550ceab34baf43fe2a246ded7a09cff8e3))
-* **ui:** Add login with google button for automatic id token retrieval ([#1044](https://github.com/googleapis/genai-toolbox/issues/1044)) ([d91bdfc](https://github.com/googleapis/genai-toolbox/commit/d91bdfcbdcbf5fcae6e17770c88c5ffba4115d67))
-
-
-### Bug Fixes
-
-* Correct the capitalization of `map` manifests ([#1139](https://github.com/googleapis/genai-toolbox/issues/1139)) ([0b0457c](https://github.com/googleapis/genai-toolbox/commit/0b0457c8e6b78f53a2f1929c05d46fb31421fbca))
-* Remove unnecessary fields from `map` parameter manifests ([#1138](https://github.com/googleapis/genai-toolbox/issues/1138)) ([fbe8c1a](https://github.com/googleapis/genai-toolbox/commit/fbe8c1a9c0f28797443bf9cb32d63bfbc1072881))
-* **tools/looker:** Add authorized invocation feature to all Looker tools ([#1091](https://github.com/googleapis/genai-toolbox/issues/1091)) ([3b1cce7](https://github.com/googleapis/genai-toolbox/commit/3b1cce72e7ff4f6b3a0a31db0564dc45b8302caa))
-* Update ui info log to reflect port ([#1125](https://github.com/googleapis/genai-toolbox/issues/1125)) ([6d691d5](https://github.com/googleapis/genai-toolbox/commit/6d691d582f18137de504d39f372c5104b7392bff))
-
 ## [0.11.0](https://github.com/googleapis/genai-toolbox/compare/v0.11.0...v0.11.0) (2025-08-05)
 
 

CONTRIBUTING.md

@@ -116,9 +116,7 @@ tools.
 * **Add a test file** under a new directory `tests/newdb`.
 * **Add pre-defined integration test suites** in the
   `/tests/newdb/newdb_test.go` that are **required** to be run as long as your
-  code contains related features. Please check each test suites for the config
-  defaults, if your source require test suites config updates, please refer to
-  [config option](./tests/option.go):
+  code contains related features:
 
      1. [RunToolGetTest][tool-get]: tests for the `GET` endpoint that returns the
             tool's manifest.
@@ -137,7 +135,7 @@ tools.
             parameters][temp-param-doc]. Only run this test if template
             parameters apply to your tool.
 
-* **Add the new database to the integration test workflow** in
+* **Add the new database to the test config** in
   [integration.cloudbuild.yaml](.ci/integration.cloudbuild.yaml).
 
 [tool-get]:
@@ -179,43 +177,6 @@ and data.
 
 #### 6. Submit a Pull Request
 
-Submit a pull request to the repository with your changes. Be sure to include a
-detailed description of your changes and any requests for long term testing
-resources.
-
-* **Title:** All pull request title should follow the formatting of
-  [Conventional 
-  Commit](https://www.conventionalcommits.org/) guidelines: `<type>[optional
-  scope]: description`. For example, if you are adding a new field in postgres
-  source, the title should be `feat(source/postgres): add support for
-  "new-field" field in postgres source`.
-  
-  Here are some commonly used `type` in this GitHub repo.
-
-  |     **type**    |                                **description**                                                        |
-  |-----------------|-------------------------------------------------------------------------------------------------------|
-  | Breaking Change | Anything with this type of a `!` after the type/scope introduces a breaking change.                   |
-  | feat            | Adding a new feature to the codebase.                                                                 |
-  | fix             | Fixing a bug or typo in the codebase. This does not include fixing docs.                              |
-  | test            | Changes made to test files.                                                                           |
-  | ci              | Changes made to the cicd configuration files or scripts.                                              |
-  | docs            | Documentation-related PRs, including fixes on docs.                                                   |
-  | chore           | Other small tasks or updates that don't fall into any of the above types.                             |
-  | refactor        | Change src code but unlike feat, there are no tests broke and no line lost coverage.                  |
-  | revert          | Revert changes made in another commit.                                                                |
-  | style           | Update src code, with only formatting and whitespace updates (e.g. code formatter or linter changes). |
-
-  Pull requests should always add scope whenever possible. The scope is
-  formatted as `<scope-type>/<scope-kind>` (e.g., `sources/postgres`, or
-  `tools/mssql-sql`).
-  
-  Ideally, **each PR covers only one scope**, if this is
-  inevitable, multiple scopes can be seaparated with a comma (e.g.
-  `sources/postgres,sources/alloydbpg`). If the PR covers multiple `scope-type`
-  (such as adding a new database), you can disregard the `scope-type`, e.g.
-  `feat(new-db): adding support for new-db source and tool`.
-
-* **PR Description:** PR description should **always** be included. It should
-  include a concise description of the changes, it's impact, along with a
-  summary of the solution. If the PR is related to a specific issue, the issue
-  number should be mentioned in the PR description (e.g. `Fixes #1`).
+* **Submit a pull request** to the repository with your changes. Be sure to
+  include a detailed description of your changes and any requests for long term
+  testing resources.

DEVELOPER.md

@@ -108,7 +108,7 @@ variables for each source.
 * AlloyDB - setup in the test project
   * AI Natural Language ([setup
     instructions](https://cloud.google.com/alloydb/docs/ai/use-natural-language-generate-sql-queries))
-    has been configured for `alloydb-ai-nl` tool tests
+    has been configured for `alloydb-a`-nl` tool tests
   * The Cloud Build service account is a user
 * Bigtable - setup in the test project
   * The Cloud Build service account is a user

README.md

@@ -33,15 +33,12 @@ documentation](https://googleapis.github.io/genai-toolbox/).
 - [Getting Started](#getting-started)
   - [Installing the server](#installing-the-server)
   - [Running the server](#running-the-server)
-    - [Homebrew Users](#homebrew-users)
   - [Integrating your application](#integrating-your-application)
 - [Configuration](#configuration)
   - [Sources](#sources)
   - [Tools](#tools)
   - [Toolsets](#toolsets)
 - [Versioning](#versioning)
-  - [Pre-1.0.0 Versioning](#pre-100-versioning)
-  - [Post-1.0.0 Versioning](#post-100-versioning)
 - [Contributing](#contributing)
 - [Community](#community)
 
@@ -117,7 +114,7 @@ To install Toolbox as a binary:
 <!-- {x-release-please-start-version} -->
 ```sh
 # see releases page for other versions
-export VERSION=0.12.0
+export VERSION=0.11.0
 curl -O https://storage.googleapis.com/genai-toolbox/v$VERSION/linux/amd64/toolbox
 chmod +x toolbox
 ```
@@ -130,7 +127,7 @@ You can also install Toolbox as a container:
 
 ```sh
 # see releases page for other versions
-export VERSION=0.12.0
+export VERSION=0.11.0
 docker pull us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:$VERSION
 ```
 
@@ -154,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.12.0
+go install github.com/googleapis/genai-toolbox@v0.11.0
 ```
 <!-- {x-release-please-end} -->
 
@@ -727,26 +724,12 @@ my_second_toolset = client.load_toolset("my_second_toolset")
 
 ## Versioning
 
-This project uses [semantic versioning](https://semver.org/) (`MAJOR.MINOR.PATCH`).
-Since the project is in a pre-release stage (version `0.x.y`), we follow the
-standard conventions for initial  development:
+This project uses [semantic versioning](https://semver.org/), including a
+`MAJOR.MINOR.PATCH` version number that increments with:
 
-### Pre-1.0.0 Versioning
-While the major version is `0`, the public API should be considered unstable.
-The version will be incremented  as follows:
-
-- **`0.MINOR.PATCH`**: The **MINOR** version is incremented when we add
-  new functionality or make breaking, incompatible API changes.
-- **`0.MINOR.PATCH`**: The **PATCH** version is incremented for
-  backward-compatible bug fixes.
-
-### Post-1.0.0 Versioning
-Once the project reaches a stable `1.0.0` release, the versioning will follow
-the more common convention:
-
-- **`MAJOR.MINOR.PATCH`**: Incremented for incompatible API changes.
-- **`MAJOR.MINOR.PATCH`**: Incremented for new, backward-compatible functionality.
-- **`MAJOR.MINOR.PATCH`**: Incremented for backward-compatible bug fixes.
+- MAJOR version when we make incompatible API changes
+- MINOR version when we add functionality in a backward compatible manner
+- PATCH version when we make backward compatible bug fixes
 
 The public API that this applies to is the CLI associated with Toolbox, the
 interactions with official SDKs, and the definitions in the `tools.yaml` file.

cmd/root.go

@@ -44,7 +44,6 @@ import (
 	// Import tool packages for side effect of registration
 	_ "github.com/googleapis/genai-toolbox/internal/tools/alloydbainl"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/bigquery/bigqueryexecutesql"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/bigquery/bigqueryforecast"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/bigquery/bigquerygetdatasetinfo"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/bigquery/bigquerygettableinfo"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/bigquery/bigquerylistdatasetids"
@@ -53,22 +52,15 @@ import (
 	_ "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/dataplexsearchaspecttypes"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/dataplex/dataplexsearchentries"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/dgraph"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/firebird/firebirdexecutesql"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/firebird/firebirdsql"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestoreadddocuments"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestoredeletedocuments"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestoregetdocuments"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestoregetrules"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestorelistcollections"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestorequerycollection"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestoreupdatedocument"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/firestore/firestorevalidaterules"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/http"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookeradddashboardelement"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookergetdashboards"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookergetdimensions"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookergetexplores"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/looker/lookergetfilters"
@@ -76,8 +68,6 @@ 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/lookermakedashboard"
-	_ "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"
@@ -98,8 +88,6 @@ import (
 	_ "github.com/googleapis/genai-toolbox/internal/tools/neo4j/neo4jcypher"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/neo4j/neo4jexecutecypher"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/neo4j/neo4jschema"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/oceanbase/oceanbaseexecutesql"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/oceanbase/oceanbasesql"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/postgres/postgresexecutesql"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/postgres/postgressql"
 	_ "github.com/googleapis/genai-toolbox/internal/tools/redis"
@@ -108,8 +96,6 @@ import (
 	_ "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/trino/trinoexecutesql"
-	_ "github.com/googleapis/genai-toolbox/internal/tools/trino/trinosql"
 	_ "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"
@@ -125,7 +111,6 @@ import (
 	_ "github.com/googleapis/genai-toolbox/internal/sources/couchbase"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/dataplex"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/dgraph"
-	_ "github.com/googleapis/genai-toolbox/internal/sources/firebird"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/firestore"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/http"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/looker"
@@ -133,13 +118,11 @@ import (
 	_ "github.com/googleapis/genai-toolbox/internal/sources/mssql"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/mysql"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/neo4j"
-	_ "github.com/googleapis/genai-toolbox/internal/sources/oceanbase"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/postgres"
 	_ "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/trino"
 	_ "github.com/googleapis/genai-toolbox/internal/sources/valkey"
 )
 
@@ -238,13 +221,7 @@ 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.")
-
-	// Fetch prebuilt tools sources to customize the help description
-	prebuiltHelp := fmt.Sprintf(
-		"Use a prebuilt tool configuration by source type. Cannot be used with --tools-file. Allowed: '%s'.",
-		strings.Join(prebuiltconfigs.GetPrebuiltSources(), "', '"),
-	)
-	flags.StringVar(&cmd.prebuiltConfig, "prebuilt", "", prebuiltHelp)
+	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.")
@@ -264,36 +241,32 @@ type ToolsFile struct {
 }
 
 // parseEnv replaces environment variables ${ENV_NAME} with their values.
-func parseEnv(input string) (string, error) {
+func parseEnv(input string) string {
 	re := regexp.MustCompile(`\$\{(\w+)\}`)
 
-	var err error
-	output := re.ReplaceAllStringFunc(input, func(match string) string {
+	return re.ReplaceAllStringFunc(input, func(match string) string {
 		parts := re.FindStringSubmatch(match)
+		if len(parts) < 2 {
+			// technically shouldn't happen
+			return match
+		}
 
 		// extract the variable name
 		variableName := parts[1]
 		if value, found := os.LookupEnv(variableName); found {
 			return value
 		}
-		err = fmt.Errorf("environment variable not found: %q", variableName)
-		return ""
+		return match
 	})
-	return output, err
 }
 
 // parseToolsFile parses the provided yaml into appropriate configs.
 func parseToolsFile(ctx context.Context, raw []byte) (ToolsFile, error) {
 	var toolsFile ToolsFile
 	// Replace environment variables if found
-	output, err := parseEnv(string(raw))
-	if err != nil {
-		return toolsFile, fmt.Errorf("error parsing environment variables: %s", err)
-	}
-	raw = []byte(output)
-
+	raw = []byte(parseEnv(string(raw)))
 	// Parse contents
-	err = yaml.UnmarshalContext(ctx, raw, &toolsFile, yaml.Strict())
+	err := yaml.UnmarshalContext(ctx, raw, &toolsFile, yaml.Strict())
 	if err != nil {
 		return toolsFile, err
 	}
@@ -829,7 +802,7 @@ func run(cmd *Command) error {
 		}
 		cmd.logger.InfoContext(ctx, "Server ready to serve!")
 		if cmd.cfg.UI {
-			cmd.logger.InfoContext(ctx, fmt.Sprintf("Toolbox UI is up and running at: http://localhost:%d/ui", cmd.cfg.Port))
+			cmd.logger.InfoContext(ctx, "Toolbox UI is up and running at: http://localhost:5000/ui")
 		}
 
 		go func() {

cmd/root_test.go

@@ -820,14 +820,13 @@ func TestParseToolFileWithAuth(t *testing.T) {
 
 func TestEnvVarReplacement(t *testing.T) {
 	ctx, err := testutils.ContextWithNewLogger()
-	t.Setenv("TestHeader", "ACTUAL_HEADER")
-	t.Setenv("API_KEY", "ACTUAL_API_KEY")
-	t.Setenv("clientId", "ACTUAL_CLIENT_ID")
-	t.Setenv("clientId2", "ACTUAL_CLIENT_ID_2")
-	t.Setenv("toolset_name", "ACTUAL_TOOLSET_NAME")
-	t.Setenv("cat_string", "cat")
-	t.Setenv("food_string", "food")
-	t.Setenv("TestHeader", "ACTUAL_HEADER")
+	os.Setenv("TestHeader", "ACTUAL_HEADER")
+	os.Setenv("API_KEY", "ACTUAL_API_KEY")
+	os.Setenv("clientId", "ACTUAL_CLIENT_ID")
+	os.Setenv("clientId2", "ACTUAL_CLIENT_ID_2")
+	os.Setenv("toolset_name", "ACTUAL_TOOLSET_NAME")
+	os.Setenv("cat_string", "cat")
+	os.Setenv("food_string", "food")
 
 	if err != nil {
 		t.Fatalf("unexpected error: %s", err)
@@ -1162,7 +1161,6 @@ func TestSingleEdit(t *testing.T) {
 }
 
 func TestPrebuiltTools(t *testing.T) {
-	// Get prebuilt configs
 	alloydb_admin_config, _ := prebuiltconfigs.Get("alloydb-postgres-admin")
 	alloydb_config, _ := prebuiltconfigs.Get("alloydb-postgres")
 	bigquery_config, _ := prebuiltconfigs.Get("bigquery")
@@ -1177,73 +1175,6 @@ func TestPrebuiltTools(t *testing.T) {
 	postgresconfig, _ := prebuiltconfigs.Get("postgres")
 	spanner_config, _ := prebuiltconfigs.Get("spanner")
 	spannerpg_config, _ := prebuiltconfigs.Get("spanner-postgres")
-
-	// Set environment variables
-	t.Setenv("API_KEY", "your_api_key")
-
-	t.Setenv("BIGQUERY_PROJECT", "your_gcp_project_id")
-	t.Setenv("DATAPLEX_PROJECT", "your_gcp_project_id")
-	t.Setenv("FIRESTORE_PROJECT", "your_gcp_project_id")
-	t.Setenv("FIRESTORE_DATABASE", "your_firestore_db_name")
-
-	t.Setenv("SPANNER_PROJECT", "your_gcp_project_id")
-	t.Setenv("SPANNER_INSTANCE", "your_spanner_instance")
-	t.Setenv("SPANNER_DATABASE", "your_spanner_db")
-
-	t.Setenv("ALLOYDB_POSTGRES_PROJECT", "your_gcp_project_id")
-	t.Setenv("ALLOYDB_POSTGRES_REGION", "your_gcp_region")
-	t.Setenv("ALLOYDB_POSTGRES_CLUSTER", "your_alloydb_cluster")
-	t.Setenv("ALLOYDB_POSTGRES_INSTANCE", "your_alloydb_instance")
-	t.Setenv("ALLOYDB_POSTGRES_DATABASE", "your_alloydb_db")
-	t.Setenv("ALLOYDB_POSTGRES_USER", "your_alloydb_user")
-	t.Setenv("ALLOYDB_POSTGRES_PASSWORD", "your_alloydb_password")
-
-	t.Setenv("CLOUD_SQL_POSTGRES_PROJECT", "your_pg_project")
-	t.Setenv("CLOUD_SQL_POSTGRES_INSTANCE", "your_pg_instance")
-	t.Setenv("CLOUD_SQL_POSTGRES_DATABASE", "your_pg_db")
-	t.Setenv("CLOUD_SQL_POSTGRES_REGION", "your_pg_region")
-	t.Setenv("CLOUD_SQL_POSTGRES_USER", "your_pg_user")
-	t.Setenv("CLOUD_SQL_POSTGRES_PASS", "your_pg_pass")
-
-	t.Setenv("CLOUD_SQL_MYSQL_PROJECT", "your_gcp_project_id")
-	t.Setenv("CLOUD_SQL_MYSQL_REGION", "your_gcp_region")
-	t.Setenv("CLOUD_SQL_MYSQL_INSTANCE", "your_instance")
-	t.Setenv("CLOUD_SQL_MYSQL_DATABASE", "your_cloudsql_mysql_db")
-	t.Setenv("CLOUD_SQL_MYSQL_USER", "your_cloudsql_mysql_user")
-	t.Setenv("CLOUD_SQL_MYSQL_PASSWORD", "your_cloudsql_mysql_password")
-
-	t.Setenv("CLOUD_SQL_MSSQL_PROJECT", "your_gcp_project_id")
-	t.Setenv("CLOUD_SQL_MSSQL_REGION", "your_gcp_region")
-	t.Setenv("CLOUD_SQL_MSSQL_INSTANCE", "your_cloudsql_mssql_instance")
-	t.Setenv("CLOUD_SQL_MSSQL_DATABASE", "your_cloudsql_mssql_db")
-	t.Setenv("CLOUD_SQL_MSSQL_IP_ADDRESS", "127.0.0.1")
-	t.Setenv("CLOUD_SQL_MSSQL_USER", "your_cloudsql_mssql_user")
-	t.Setenv("CLOUD_SQL_MSSQL_PASSWORD", "your_cloudsql_mssql_password")
-	t.Setenv("CLOUD_SQL_POSTGRES_PASSWORD", "your_cloudsql_pg_password")
-
-	t.Setenv("POSTGRES_HOST", "localhost")
-	t.Setenv("POSTGRES_PORT", "5432")
-	t.Setenv("POSTGRES_DATABASE", "your_postgres_db")
-	t.Setenv("POSTGRES_USER", "your_postgres_user")
-	t.Setenv("POSTGRES_PASSWORD", "your_postgres_password")
-
-	t.Setenv("MYSQL_HOST", "localhost")
-	t.Setenv("MYSQL_PORT", "3306")
-	t.Setenv("MYSQL_DATABASE", "your_mysql_db")
-	t.Setenv("MYSQL_USER", "your_mysql_user")
-	t.Setenv("MYSQL_PASSWORD", "your_mysql_password")
-
-	t.Setenv("MSSQL_HOST", "localhost")
-	t.Setenv("MSSQL_PORT", "1433")
-	t.Setenv("MSSQL_DATABASE", "your_mssql_db")
-	t.Setenv("MSSQL_USER", "your_mssql_user")
-	t.Setenv("MSSQL_PASSWORD", "your_mssql_password")
-
-	t.Setenv("LOOKER_BASE_URL", "https://your_company.looker.com")
-	t.Setenv("LOOKER_CLIENT_ID", "your_looker_client_id")
-	t.Setenv("LOOKER_CLIENT_SECRET", "your_looker_client_secret")
-	t.Setenv("LOOKER_VERIFY_SSL", "true")
-
 	ctx, err := testutils.ContextWithNewLogger()
 	if err != nil {
 		t.Fatalf("unexpected error: %s", err)
@@ -1259,7 +1190,7 @@ func TestPrebuiltTools(t *testing.T) {
 			wantToolset: server.ToolsetConfigs{
 				"alloydb-postgres-admin-tools": tools.ToolsetConfig{
 					Name:      "alloydb-postgres-admin-tools",
-					ToolNames: []string{"alloydb-create-cluster", "alloydb-operations-get", "alloydb-create-instance", "alloydb-list-clusters", "alloydb-list-instances", "alloydb-list-users", "alloydb-create-user"},
+					ToolNames: []string{"alloydb-create-cluster", "alloydb-operations-get", "alloydb-create-instance"},
 				},
 			},
 		},
@@ -1279,7 +1210,7 @@ func TestPrebuiltTools(t *testing.T) {
 			wantToolset: server.ToolsetConfigs{
 				"bigquery-database-tools": tools.ToolsetConfig{
 					Name:      "bigquery-database-tools",
-					ToolNames: []string{"execute_sql", "forecast", "get_dataset_info", "get_table_info", "list_dataset_ids", "list_table_ids"},
+					ToolNames: []string{"execute_sql", "get_dataset_info", "get_table_info", "list_dataset_ids", "list_table_ids"},
 				},
 			},
 		},
@@ -1319,7 +1250,7 @@ func TestPrebuiltTools(t *testing.T) {
 			wantToolset: server.ToolsetConfigs{
 				"dataplex-tools": tools.ToolsetConfig{
 					Name:      "dataplex-tools",
-					ToolNames: []string{"dataplex_search_entries", "dataplex_lookup_entry", "dataplex_search_aspect_types"},
+					ToolNames: []string{"dataplex_search_entries", "dataplex_lookup_entry"},
 				},
 			},
 		},
@@ -1329,7 +1260,7 @@ func TestPrebuiltTools(t *testing.T) {
 			wantToolset: server.ToolsetConfigs{
 				"firestore-database-tools": tools.ToolsetConfig{
 					Name:      "firestore-database-tools",
-					ToolNames: []string{"firestore-get-documents", "firestore-add-documents", "firestore-update-document", "firestore-list-collections", "firestore-delete-documents", "firestore-query-collection", "firestore-get-rules", "firestore-validate-rules"},
+					ToolNames: []string{"firestore-get-documents", "firestore-list-collections", "firestore-delete-documents", "firestore-query-collection", "firestore-get-rules", "firestore-validate-rules"},
 				},
 			},
 		},
@@ -1359,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", "query_url", "get_looks", "run_look", "make_look", "get_dashboards", "make_dashboard", "add_dashboard_element"},
+					ToolNames: []string{"get_models", "get_explores", "get_dimensions", "get_measures", "get_filters", "get_parameters", "query", "query_sql", "query_url", "get_looks", "run_look"},
 				},
 			},
 		},

cmd/version.txt

@@ -1 +1 @@
-0.12.0
+0.11.0

docs/en/about/faq.md

@@ -7,11 +7,11 @@ description: Frequently asked questions about Toolbox.
 
 ## How can I deploy or run Toolbox?
 
-MCP Toolbox for Databases is open-source and can be run or deployed to a
+MCP Toolbox for Databases is open-source and can be ran or deployed to a
 multitude of environments. For convenience, we release [compiled binaries and
 docker images][release-notes] (but you can always compile yourself as well!).
 
-For detailed instructions, check out these resources:
+For detailed instructions, check our these resources:
 
 - [Quickstart: How to Run Locally](../getting-started/local_quickstart.md)
 - [Deploy to Cloud Run](../how-to/deploy_toolbox.md)

docs/en/getting-started/colab_quickstart.ipynb

@@ -234,7 +234,7 @@
       },
       "outputs": [],
       "source": [
-        "version = \"0.12.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/configure.md

@@ -45,7 +45,7 @@ For more details on configuring different types of sources, see the
 
 ### Tools
 
-The `tools` section of your `tools.yaml` defines the actions your agent can
+The `tools` section of your `tools.yaml` define your the actions your agent can
 take: what kind of tool it is, which source(s) it affects, what parameters it
 uses, etc.
 
@@ -76,7 +76,7 @@ toolsets:
   my_first_toolset:
     - my_first_tool
     - my_second_tool
-  my_second_toolset:
+   my_second_toolset:
     - my_second_tool
     - my_third_tool
 ```

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.12.0
+export VERSION=0.11.0
 curl -O https://storage.googleapis.com/genai-toolbox/v$VERSION/linux/amd64/toolbox
 chmod +x toolbox
 ```
@@ -97,7 +97,7 @@ You can also install Toolbox as a container:
 
 ```sh
 # see releases page for other versions
-export VERSION=0.12.0
+export VERSION=0.11.0
 docker pull us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:$VERSION
 ```
 
@@ -115,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.12.0
+go install github.com/googleapis/genai-toolbox@v0.11.0
 ```
 
 {{% /tab %}}
@@ -139,7 +139,7 @@ Toolbox enables dynamic reloading by default. To disable, use the
 #### 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/toolbox-ui/index.md).
+with features such as authorized parameters. To learn more, visit [Toolbox UI](../../how-to/use-toolbox-ui/index.md).
 
 ```sh
 ./toolbox --ui

docs/en/getting-started/local_quickstart.md

@@ -18,13 +18,265 @@ This guide assumes you have already done the following:
 1. Installed [PostgreSQL 16+ and the `psql` client][install-postgres].
 
 ### Cloud Setup (Optional)
-{{< regionInclude "quickstart/shared/cloud_setup.md" "cloud_setup" >}}
+
+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)
+1. Set your project and enable Vertex AI
+
+    ```bash
+    gcloud config set project YOUR_PROJECT_ID
+    gcloud services enable aiplatform.googleapis.com
+    ```
+
+[install-python]: https://wiki.python.org/moin/BeginnersGuide/Download
+[install-pip]: https://pip.pypa.io/en/stable/installation/
+[install-venv]: https://packaging.python.org/en/latest/tutorials/installing-packages/#creating-virtual-environments
+[install-postgres]: https://www.postgresql.org/download/
 
 ## Step 1: Set up your database
-{{< regionInclude "quickstart/shared/database_setup.md" "database_setup" >}}
+
+In this section, we will create a database, insert some data that needs to be
+accessed by our agent, and create a database user for Toolbox to connect with.
+
+1. Connect to postgres using the `psql` command:
+
+    ```bash
+    psql -h 127.0.0.1 -U postgres
+    ```
+
+    Here, `postgres` denotes the default postgres superuser.
+
+    {{< notice info >}}
+
+#### **Having trouble connecting?**
+
+* **Password Prompt:** If you are prompted for a password for the `postgres`
+  user and do not know it (or a blank password doesn't work), your PostgreSQL
+  installation might require a password or a different authentication method.
+* **`FATAL: role "postgres" does not exist`:** This error means the default
+  `postgres` superuser role isn't available under that name on your system.
+* **`Connection refused`:** Ensure your PostgreSQL server is actually running.
+  You can typically check with `sudo systemctl status postgresql` and start it
+  with `sudo systemctl start postgresql` on Linux systems.
+
+<br/>
+
+#### **Common Solution**
+
+For password issues or if the `postgres` role seems inaccessible directly, try
+switching to the `postgres` operating system user first. This user often has
+permission to connect without a password for local connections (this is called
+peer authentication).
+
+```bash
+sudo -i -u postgres
+psql -h 127.0.0.1
+```
+
+Once you are in the `psql` shell using this method, you can proceed with the
+database creation steps below. Afterwards, type `\q` to exit `psql`, and then
+`exit` to return to your normal user shell.
+
+If desired, once connected to `psql` as the `postgres` OS user, you can set a
+password for the `postgres` *database* user using: `ALTER USER postgres WITH
+PASSWORD 'your_chosen_password';`. This would allow direct connection with `-U
+postgres` and a password next time.
+    {{< /notice >}}
+
+1. Create a new database and a new user:
+
+    {{< notice tip >}}
+  For a real application, it's best to follow the principle of least permission
+  and only grant the privileges your application needs.
+    {{< /notice >}}
+
+    ```sql
+      CREATE USER toolbox_user WITH PASSWORD 'my-password';
+
+      CREATE DATABASE toolbox_db;
+      GRANT ALL PRIVILEGES ON DATABASE toolbox_db TO toolbox_user;
+
+      ALTER DATABASE toolbox_db OWNER TO toolbox_user;
+    ```
+
+1. End the database session:
+
+    ```bash
+    \q
+    ```
+
+    (If you used `sudo -i -u postgres` and then `psql`, remember you might also
+    need to type `exit` after `\q` to leave the `postgres` user's shell
+    session.)
+
+1. Connect to your database with your new user:
+
+    ```bash
+    psql -h 127.0.0.1 -U toolbox_user -d toolbox_db
+    ```
+
+1. Create a table using the following command:
+
+    ```sql
+    CREATE TABLE hotels(
+      id            INTEGER NOT NULL PRIMARY KEY,
+      name          VARCHAR NOT NULL,
+      location      VARCHAR NOT NULL,
+      price_tier    VARCHAR NOT NULL,
+      checkin_date  DATE    NOT NULL,
+      checkout_date DATE    NOT NULL,
+      booked        BIT     NOT NULL
+    );
+    ```
+
+1. Insert data into the table.
+
+    ```sql
+    INSERT INTO hotels(id, name, location, price_tier, checkin_date, checkout_date, booked)
+    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'),
+      (4, 'Radisson Blu Lucerne', 'Lucerne', 'Midscale', '2024-04-24', '2024-04-05', B'0'),
+      (5, 'Best Western Bern', 'Bern', 'Upper Midscale', '2024-04-23', '2024-04-01', B'0'),
+      (6, 'InterContinental Geneva', 'Geneva', 'Luxury', '2024-04-23', '2024-04-28', B'0'),
+      (7, 'Sheraton Zurich', 'Zurich', 'Upper Upscale', '2024-04-27', '2024-04-02', B'0'),
+      (8, 'Holiday Inn Basel', 'Basel', 'Upper Midscale', '2024-04-24', '2024-04-09', B'0'),
+      (9, 'Courtyard Zurich', 'Zurich', 'Upscale', '2024-04-03', '2024-04-13', B'0'),
+      (10, 'Comfort Inn Bern', 'Bern', 'Midscale', '2024-04-04', '2024-04-16', B'0');
+    ```
+
+1. End the database session:
+
+    ```bash
+    \q
+    ```
 
 ## Step 2: Install and configure Toolbox
-{{< regionInclude "quickstart/shared/configure_toolbox.md" "configure_toolbox" >}}
+
+In this section, we will download Toolbox, configure our tools in a
+`tools.yaml`, and then run the Toolbox server.
+
+1. Download the latest version of Toolbox as a binary:
+
+    {{< notice tip >}}
+  Select the
+  [correct binary](https://github.com/googleapis/genai-toolbox/releases)
+  corresponding to your OS and CPU architecture.
+    {{< /notice >}}
+    <!-- {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.11.0/$OS/toolbox
+    ```
+    <!-- {x-release-please-end} -->
+
+1. Make the binary executable:
+
+    ```bash
+    chmod +x toolbox
+    ```
+
+1. Write the following into a `tools.yaml` file. Be sure to update any fields
+   such as `user`, `password`, or `database` that you may have customized in the
+   previous step.
+
+    {{< notice tip >}}
+  In practice, use environment variable replacement with the format ${ENV_NAME}
+  instead of hardcoding your secrets into the configuration file.
+    {{< /notice >}}
+
+    ```yaml
+    sources:
+      my-pg-source:
+        kind: postgres
+        host: 127.0.0.1
+        port: 5432
+        database: toolbox_db
+        user: ${USER_NAME}
+        password: ${PASSWORD}
+    tools:
+      search-hotels-by-name:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Search for hotels based on name.
+        parameters:
+          - name: name
+            type: string
+            description: The name of the hotel.
+        statement: SELECT * FROM hotels WHERE name ILIKE '%' || $1 || '%';
+      search-hotels-by-location:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Search for hotels based on location.
+        parameters:
+          - name: location
+            type: string
+            description: The location of the hotel.
+        statement: SELECT * FROM hotels WHERE location ILIKE '%' || $1 || '%';
+      book-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: >-
+           Book a hotel by its ID. If the hotel is successfully booked, returns a NULL, raises an error if not.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to book.
+        statement: UPDATE hotels SET booked = B'1' WHERE id = $1;
+      update-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: >-
+          Update a hotel's check-in and check-out dates by its ID. Returns a message
+          indicating  whether the hotel was successfully updated or not.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to update.
+          - name: checkin_date
+            type: string
+            description: The new check-in date of the hotel.
+          - name: checkout_date
+            type: string
+            description: The new check-out date of the hotel.
+        statement: >-
+          UPDATE hotels SET checkin_date = CAST($2 as date), checkout_date = CAST($3
+          as date) WHERE id = $1;
+      cancel-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Cancel a hotel by its ID.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to cancel.
+        statement: UPDATE hotels SET booked = B'0' WHERE id = $1;
+   toolsets:
+      my-toolset:
+        - search-hotels-by-name
+        - search-hotels-by-location
+        - book-hotel
+        - update-hotel
+        - cancel-hotel
+    ```
+
+    For more info on tools, check out the `Resources` section of the docs.
+
+1. Run the Toolbox server, pointing to the `tools.yaml` file created earlier:
+
+    ```bash
+    ./toolbox --tools-file "tools.yaml"
+    ```
+
+    {{< notice note >}}
+    Toolbox enables dynamic reloading by default. To disable, use the
+    `--disable-reload` flag.
+    {{< /notice >}}
 
 ## Step 3: Connect your agent to Toolbox
 
@@ -142,7 +394,7 @@ async def main():
       )
 
       queries = [
-          "Find hotels in Basel with Basel in its name.",
+          "Find hotels in Basel with Basel in it's name.",
           "Can you book the Hilton Basel for me?",
           "Oh wait, this is too expensive. Please cancel it and book the Hyatt Regency instead.",
           "My check in dates would be from April 10, 2024 to April 19, 2024.",
@@ -193,7 +445,7 @@ prompt = """
 """
 
 queries = [
-    "Find hotels in Basel with Basel in its name.",
+    "Find hotels in Basel with Basel in it's name.",
     "Can you book the Hilton Basel for me?",
     "Oh wait, this is too expensive. Please cancel it and book the Hyatt Regency instead.",
     "My check in dates would be from April 10, 2024 to April 19, 2024.",
@@ -246,7 +498,7 @@ prompt = """
 """
 
 queries = [
-    "Find hotels in Basel with Basel in its name.",
+    "Find hotels in Basel with Basel in it's name.",
     "Can you book the Hilton Basel for me?",
     "Oh wait, this is too expensive. Please cancel it and book the Hyatt Regency instead.",
     "My check in dates would be from April 10, 2024 to April 19, 2024.",
@@ -309,7 +561,7 @@ prompt = """
 """
 
 queries = [
-    "Find hotels in Basel with Basel in its name.",
+    "Find hotels in Basel with Basel in it's name.",
     "Please book the hotel Hilton Basel for me.",
     "This is too expensive. Please cancel it.",
     "Please book Hyatt Regency for me",

docs/en/getting-started/local_quickstart_go.md

@@ -13,17 +13,266 @@ This guide assumes you have already done the following:
 1. Installed [Go (v1.24.2 or higher)].
 1. Installed [PostgreSQL 16+ and the `psql` client][install-postgres].
 
+### 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:
+
+1. [Install the Google Cloud CLI]
+1. [Set up Application Default Credentials (ADC)]
+1. Set your project and enable Vertex AI
+
+    ```bash
+    gcloud config set project YOUR_PROJECT_ID
+    gcloud services enable aiplatform.googleapis.com
+    ```
+
 [Go (v1.24.2 or higher)]: https://go.dev/doc/install
 [install-postgres]: https://www.postgresql.org/download/
-
-### Cloud Setup (Optional)
-{{< regionInclude "quickstart/shared/cloud_setup.md" "cloud_setup" >}}
+[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
 
 ## Step 1: Set up your database
-{{< regionInclude "quickstart/shared/database_setup.md" "database_setup" >}}
+
+In this section, we will create a database, insert some data that needs to be
+accessed by our agent, and create a database user for Toolbox to connect with.
+
+1. Connect to postgres using the `psql` command:
+
+    ```bash
+    psql -h 127.0.0.1 -U postgres
+    ```
+
+    Here, `postgres` denotes the default postgres superuser.
+
+    {{< notice info >}}
+
+#### **Having trouble connecting?**
+
+* **Password Prompt:** If you are prompted for a password for the `postgres`
+  user and do not know it (or a blank password doesn't work), your PostgreSQL
+  installation might require a password or a different authentication method.
+* **`FATAL: role "postgres" does not exist`:** This error means the default
+  `postgres` superuser role isn't available under that name on your system.
+* **`Connection refused`:** Ensure your PostgreSQL server is actually running.
+  You can typically check with `sudo systemctl status postgresql` and start it
+  with `sudo systemctl start postgresql` on Linux systems.
+
+<br/>
+
+#### **Common Solution**
+
+For password issues or if the `postgres` role seems inaccessible directly, try
+switching to the `postgres` operating system user first. This user often has
+permission to connect without a password for local connections (this is called
+peer authentication).
+
+```bash
+sudo -i -u postgres
+psql -h 127.0.0.1
+```
+
+Once you are in the `psql` shell using this method, you can proceed with the
+database creation steps below. Afterwards, type `\q` to exit `psql`, and then
+`exit` to return to your normal user shell.
+
+If desired, once connected to `psql` as the `postgres` OS user, you can set a
+password for the `postgres` *database* user using: `ALTER USER postgres WITH
+PASSWORD 'your_chosen_password';`. This would allow direct connection with `-U
+postgres` and a password next time.
+    {{< /notice >}}
+
+1. Create a new database and a new user:
+
+    {{< notice tip >}}
+  For a real application, it's best to follow the principle of least permission
+  and only grant the privileges your application needs.
+    {{< /notice >}}
+
+    ```sql
+      CREATE USER toolbox_user WITH PASSWORD 'my-password';
+
+      CREATE DATABASE toolbox_db;
+      GRANT ALL PRIVILEGES ON DATABASE toolbox_db TO toolbox_user;
+
+      ALTER DATABASE toolbox_db OWNER TO toolbox_user;
+    ```
+
+1. End the database session:
+
+    ```bash
+    \q
+    ```
+
+    (If you used `sudo -i -u postgres` and then `psql`, remember you might also
+    need to type `exit` after `\q` to leave the `postgres` user's shell
+    session.)
+
+1. Connect to your database with your new user:
+
+    ```bash
+    psql -h 127.0.0.1 -U toolbox_user -d toolbox_db
+    ```
+
+1. Create a table using the following command:
+
+    ```sql
+    CREATE TABLE hotels(
+      id            INTEGER NOT NULL PRIMARY KEY,
+      name          VARCHAR NOT NULL,
+      location      VARCHAR NOT NULL,
+      price_tier    VARCHAR NOT NULL,
+      checkin_date  DATE    NOT NULL,
+      checkout_date DATE    NOT NULL,
+      booked        BIT     NOT NULL
+    );
+    ```
+
+1. Insert data into the table.
+
+    ```sql
+    INSERT INTO hotels(id, name, location, price_tier, checkin_date, checkout_date, booked)
+    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'),
+      (4, 'Radisson Blu Lucerne', 'Lucerne', 'Midscale', '2024-04-24', '2024-04-05', B'0'),
+      (5, 'Best Western Bern', 'Bern', 'Upper Midscale', '2024-04-23', '2024-04-01', B'0'),
+      (6, 'InterContinental Geneva', 'Geneva', 'Luxury', '2024-04-23', '2024-04-28', B'0'),
+      (7, 'Sheraton Zurich', 'Zurich', 'Upper Upscale', '2024-04-27', '2024-04-02', B'0'),
+      (8, 'Holiday Inn Basel', 'Basel', 'Upper Midscale', '2024-04-24', '2024-04-09', B'0'),
+      (9, 'Courtyard Zurich', 'Zurich', 'Upscale', '2024-04-03', '2024-04-13', B'0'),
+      (10, 'Comfort Inn Bern', 'Bern', 'Midscale', '2024-04-04', '2024-04-16', B'0');
+    ```
+
+1. End the database session:
+
+    ```bash
+    \q
+    ```
 
 ## Step 2: Install and configure Toolbox
-{{< regionInclude "quickstart/shared/configure_toolbox.md" "configure_toolbox" >}}
+
+In this section, we will download Toolbox, configure our tools in a
+`tools.yaml`, and then run the Toolbox server.
+
+1. Download the latest version of Toolbox as a binary:
+
+    {{< notice tip >}}
+  Select the
+  [correct binary](https://github.com/googleapis/genai-toolbox/releases)
+  corresponding to your OS and CPU architecture.
+    {{< /notice >}}
+    <!-- {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.11.0/$OS/toolbox
+    ```
+    <!-- {x-release-please-end} -->
+
+1. Make the binary executable:
+
+    ```bash
+    chmod +x toolbox
+    ```
+
+1. Write the following into a `tools.yaml` file. Be sure to update any fields
+   such as `user`, `password`, or `database` that you may have customized in the
+   previous step.
+
+    {{< notice tip >}}
+  In practice, use environment variable replacement with the format ${ENV_NAME}
+  instead of hardcoding your secrets into the configuration file.
+    {{< /notice >}}
+
+    ```yaml
+    sources:
+      my-pg-source:
+        kind: postgres
+        host: 127.0.0.1
+        port: 5432
+        database: toolbox_db
+        user: ${USER_NAME}
+        password: ${PASSWORD}
+    tools:
+      search-hotels-by-name:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Search for hotels based on name.
+        parameters:
+          - name: name
+            type: string
+            description: The name of the hotel.
+        statement: SELECT * FROM hotels WHERE name ILIKE '%' || $1 || '%';
+      search-hotels-by-location:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Search for hotels based on location.
+        parameters:
+          - name: location
+            type: string
+            description: The location of the hotel.
+        statement: SELECT * FROM hotels WHERE location ILIKE '%' || $1 || '%';
+      book-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: >-
+           Book a hotel by its ID. If the hotel is successfully booked, returns a NULL, raises an error if not.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to book.
+        statement: UPDATE hotels SET booked = B'1' WHERE id = $1;
+      update-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: >-
+          Update a hotel's check-in and check-out dates by its ID. Returns a message
+          indicating  whether the hotel was successfully updated or not.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to update.
+          - name: checkin_date
+            type: string
+            description: The new check-in date of the hotel.
+          - name: checkout_date
+            type: string
+            description: The new check-out date of the hotel.
+        statement: >-
+          UPDATE hotels SET checkin_date = CAST($2 as date), checkout_date = CAST($3
+          as date) WHERE id = $1;
+      cancel-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Cancel a hotel by its ID.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to cancel.
+        statement: UPDATE hotels SET booked = B'0' WHERE id = $1;
+   toolsets:
+      my-toolset:
+        - search-hotels-by-name
+        - search-hotels-by-location
+        - book-hotel
+        - update-hotel
+        - cancel-hotel
+    ```
+
+    For more info on tools, check out the `Resources` section of the docs.
+
+1. Run the Toolbox server, pointing to the `tools.yaml` file created earlier:
+
+    ```bash
+    ./toolbox --tools-file "tools.yaml"
+    ```
+
+  {{< notice note >}}
+    Toolbox enables dynamic reloading by default. To disable, use the
+    `--disable-reload` flag.
+  {{< /notice >}}
 
 ## Step 3: Connect your agent to Toolbox
 
@@ -623,7 +872,7 @@ func main() {
 			log.Println("No function call")
 		}
 
-		// If there was a function call, continue the conversation
+		// If there is a was a function call, continue the conversation
 		params.Messages = append(params.Messages, completion.Choices[0].Message.ToParam())
 		for _, toolCall := range toolCalls {
 

docs/en/getting-started/local_quickstart_js.md

@@ -3,7 +3,7 @@ title: "JS Quickstart (Local)"
 type: docs
 weight: 3
 description: >
-  How to get started running Toolbox locally with [JavaScript](https://github.com/googleapis/mcp-toolbox-sdk-js), PostgreSQL, and orchestration frameworks such as [LangChain](https://js.langchain.com/docs/introduction/), [GenkitJS](https://genkit.dev/docs/get-started/),  [LlamaIndex](https://ts.llamaindex.ai/) and [GoogleGenAI](https://github.com/googleapis/js-genai).
+  How to get started running Toolbox locally with [JavaScript](https://github.com/googleapis/mcp-toolbox-sdk-js), PostgreSQL, and orchestration frameworks such as [LangChain](https://js.langchain.com/docs/introduction/), [GenkitJS](https://genkit.dev/docs/get-started/), and [LlamaIndex](https://ts.llamaindex.ai/).
 ---
 
 ## Before you begin
@@ -13,17 +13,265 @@ This guide assumes you have already done the following:
 1. Installed [Node.js (v18 or higher)].
 1. Installed [PostgreSQL 16+ and the `psql` client][install-postgres].
 
+### 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:
+
+1. [Install the Google Cloud CLI]
+1. [Set up Application Default Credentials (ADC)]
+1. Set your project and enable Vertex AI
+
+    ```bash
+    gcloud config set project YOUR_PROJECT_ID
+    gcloud services enable aiplatform.googleapis.com
+    ```
+
 [Node.js (v18 or higher)]: https://nodejs.org/
 [install-postgres]: https://www.postgresql.org/download/
-
-### Cloud Setup (Optional)
-{{< regionInclude "quickstart/shared/cloud_setup.md" "cloud_setup" >}}
+[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
 
 ## Step 1: Set up your database
-{{< regionInclude "quickstart/shared/database_setup.md" "database_setup" >}}
+
+In this section, we will create a database, insert some data that needs to be
+accessed by our agent, and create a database user for Toolbox to connect with.
+
+1. Connect to postgres using the `psql` command:
+
+    ```bash
+    psql -h 127.0.0.1 -U postgres
+    ```
+
+    Here, `postgres` denotes the default postgres superuser.
+
+    {{< notice info >}}
+
+#### **Having trouble connecting?**
+
+* **Password Prompt:** If you are prompted for a password for the `postgres`
+  user and do not know it (or a blank password doesn't work), your PostgreSQL
+  installation might require a password or a different authentication method.
+* **`FATAL: role "postgres" does not exist`:** This error means the default
+  `postgres` superuser role isn't available under that name on your system.
+* **`Connection refused`:** Ensure your PostgreSQL server is actually running.
+  You can typically check with `sudo systemctl status postgresql` and start it
+  with `sudo systemctl start postgresql` on Linux systems.
+
+<br/>
+
+#### **Common Solution**
+
+For password issues or if the `postgres` role seems inaccessible directly, try
+switching to the `postgres` operating system user first. This user often has
+permission to connect without a password for local connections (this is called
+peer authentication).
+
+```bash
+sudo -i -u postgres
+psql -h 127.0.0.1
+```
+
+Once you are in the `psql` shell using this method, you can proceed with the
+database creation steps below. Afterwards, type `\q` to exit `psql`, and then
+`exit` to return to your normal user shell.
+
+If desired, once connected to `psql` as the `postgres` OS user, you can set a
+password for the `postgres` *database* user using: `ALTER USER postgres WITH
+PASSWORD 'your_chosen_password';`. This would allow direct connection with `-U
+postgres` and a password next time.
+    {{< /notice >}}
+
+1. Create a new database and a new user:
+
+    {{< notice tip >}}
+  For a real application, it's best to follow the principle of least permission
+  and only grant the privileges your application needs.
+    {{< /notice >}}
+
+    ```sql
+      CREATE USER toolbox_user WITH PASSWORD 'my-password';
+
+      CREATE DATABASE toolbox_db;
+      GRANT ALL PRIVILEGES ON DATABASE toolbox_db TO toolbox_user;
+
+      ALTER DATABASE toolbox_db OWNER TO toolbox_user;
+    ```
+
+1. End the database session:
+
+    ```bash
+    \q
+    ```
+
+    (If you used `sudo -i -u postgres` and then `psql`, remember you might also
+    need to type `exit` after `\q` to leave the `postgres` user's shell
+    session.)
+
+1. Connect to your database with your new user:
+
+    ```bash
+    psql -h 127.0.0.1 -U toolbox_user -d toolbox_db
+    ```
+
+1. Create a table using the following command:
+
+    ```sql
+    CREATE TABLE hotels(
+      id            INTEGER NOT NULL PRIMARY KEY,
+      name          VARCHAR NOT NULL,
+      location      VARCHAR NOT NULL,
+      price_tier    VARCHAR NOT NULL,
+      checkin_date  DATE    NOT NULL,
+      checkout_date DATE    NOT NULL,
+      booked        BIT     NOT NULL
+    );
+    ```
+
+1. Insert data into the table.
+
+    ```sql
+    INSERT INTO hotels(id, name, location, price_tier, checkin_date, checkout_date, booked)
+    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'),
+      (4, 'Radisson Blu Lucerne', 'Lucerne', 'Midscale', '2024-04-24', '2024-04-05', B'0'),
+      (5, 'Best Western Bern', 'Bern', 'Upper Midscale', '2024-04-23', '2024-04-01', B'0'),
+      (6, 'InterContinental Geneva', 'Geneva', 'Luxury', '2024-04-23', '2024-04-28', B'0'),
+      (7, 'Sheraton Zurich', 'Zurich', 'Upper Upscale', '2024-04-27', '2024-04-02', B'0'),
+      (8, 'Holiday Inn Basel', 'Basel', 'Upper Midscale', '2024-04-24', '2024-04-09', B'0'),
+      (9, 'Courtyard Zurich', 'Zurich', 'Upscale', '2024-04-03', '2024-04-13', B'0'),
+      (10, 'Comfort Inn Bern', 'Bern', 'Midscale', '2024-04-04', '2024-04-16', B'0');
+    ```
+
+1. End the database session:
+
+    ```bash
+    \q
+    ```
 
 ## Step 2: Install and configure Toolbox
-{{< regionInclude "quickstart/shared/configure_toolbox.md" "configure_toolbox" >}}
+
+In this section, we will download Toolbox, configure our tools in a
+`tools.yaml`, and then run the Toolbox server.
+
+1. Download the latest version of Toolbox as a binary:
+
+    {{< notice tip >}}
+  Select the
+  [correct binary](https://github.com/googleapis/genai-toolbox/releases)
+  corresponding to your OS and CPU architecture.
+    {{< /notice >}}
+    <!-- {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.11.0/$OS/toolbox
+    ```
+    <!-- {x-release-please-end} -->
+
+1. Make the binary executable:
+
+    ```bash
+    chmod +x toolbox
+    ```
+
+1. Write the following into a `tools.yaml` file. Be sure to update any fields
+   such as `user`, `password`, or `database` that you may have customized in the
+   previous step.
+
+    {{< notice tip >}}
+  In practice, use environment variable replacement with the format ${ENV_NAME}
+  instead of hardcoding your secrets into the configuration file.
+    {{< /notice >}}
+
+    ```yaml
+    sources:
+      my-pg-source:
+        kind: postgres
+        host: 127.0.0.1
+        port: 5432
+        database: toolbox_db
+        user: ${USER_NAME}
+        password: ${PASSWORD}
+    tools:
+      search-hotels-by-name:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Search for hotels based on name.
+        parameters:
+          - name: name
+            type: string
+            description: The name of the hotel.
+        statement: SELECT * FROM hotels WHERE name ILIKE '%' || $1 || '%';
+      search-hotels-by-location:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Search for hotels based on location.
+        parameters:
+          - name: location
+            type: string
+            description: The location of the hotel.
+        statement: SELECT * FROM hotels WHERE location ILIKE '%' || $1 || '%';
+      book-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: >-
+           Book a hotel by its ID. If the hotel is successfully booked, returns a NULL, raises an error if not.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to book.
+        statement: UPDATE hotels SET booked = B'1' WHERE id = $1;
+      update-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: >-
+          Update a hotel's check-in and check-out dates by its ID. Returns a message
+          indicating  whether the hotel was successfully updated or not.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to update.
+          - name: checkin_date
+            type: string
+            description: The new check-in date of the hotel.
+          - name: checkout_date
+            type: string
+            description: The new check-out date of the hotel.
+        statement: >-
+          UPDATE hotels SET checkin_date = CAST($2 as date), checkout_date = CAST($3
+          as date) WHERE id = $1;
+      cancel-hotel:
+        kind: postgres-sql
+        source: my-pg-source
+        description: Cancel a hotel by its ID.
+        parameters:
+          - name: hotel_id
+            type: string
+            description: The ID of the hotel to cancel.
+        statement: UPDATE hotels SET booked = B'0' WHERE id = $1;
+   toolsets:
+      my-toolset:
+        - search-hotels-by-name
+        - search-hotels-by-location
+        - book-hotel
+        - update-hotel
+        - cancel-hotel
+    ```
+
+    For more info on tools, check out the `Resources` section of the docs.
+
+1. Run the Toolbox server, pointing to the `tools.yaml` file created earlier:
+
+    ```bash
+    ./toolbox --tools-file "tools.yaml"
+    ```
+
+  {{< notice note >}}
+    Toolbox enables dynamic reloading by default. To disable, use the `--disable-reload` flag.
+  {{< /notice >}}
 
 ## Step 3: Connect your agent to Toolbox
 
@@ -46,17 +294,14 @@ from Toolbox.
 
    {{< tabpane persist=header >}}
 {{< tab header="LangChain" lang="bash" >}}
-npm install langchain @langchain/google-genai
+npm install langchain @langchain/google-vertexai
 {{< /tab >}}
 {{< tab header="GenkitJS" lang="bash" >}}
-npm install genkit @genkit-ai/googleai
+npm install genkit @genkit-ai/vertexai
 {{< /tab >}}
 {{< tab header="LlamaIndex" lang="bash" >}}
 npm install llamaindex @llamaindex/google @llamaindex/workflow
 {{< /tab >}}
-{{< tab header="GoogleGenAI" lang="bash" >}}
-npm install @google/genai 
-{{< /tab >}}
 {{< /tabpane >}}
 
 1. Create a new file named `hotelAgent.js` and copy the following code to create an agent:
@@ -64,7 +309,7 @@ npm install @google/genai
     {{< tabpane persist=header >}}
 {{< tab header="LangChain" lang="js" >}}
 
-import { ChatGoogleGenerativeAI } from "@langchain/google-genai";
+import { ChatVertexAI } from "@langchain/google-vertexai";
 import { ToolboxClient } from "@toolbox-sdk/core";
 import { tool } from "@langchain/core/tools";
 import { createReactAgent } from "@langchain/langgraph/prebuilt";
@@ -91,7 +336,7 @@ const queries = [
 ];
 
 async function runApplication() {
-  const model = new ChatGoogleGenerativeAI({
+  const model = new ChatVertexAI({
     model: "gemini-2.0-flash",
   });
 
@@ -320,130 +565,6 @@ main();
 
 {{< /tab >}}
 
-{{< tab header="GoogleGenAI" lang="js" >}}
-import { GoogleGenAI } from "@google/genai";
-import { ToolboxClient } from "@toolbox-sdk/core";
-
-
-const TOOLBOX_URL = "http://127.0.0.1:5000"; // Update if needed
-const GOOGLE_API_KEY = 'enter your api here'; // Replace it with your API key
-
-const prompt = `
-You're a helpful hotel assistant. You handle hotel searching, booking, and
-cancellations. When the user searches for a hotel, you MUST use the available tools to find information. Mention its name, id,
-location and price tier. Always mention hotel id while performing any
-searches. This is very important for any operations. For any bookings or
-cancellations, please provide the appropriate confirmation. Be sure to
-update checkin or checkout dates if mentioned by the user.
-Don't ask for confirmations from the user.
-`;
-
-const queries = [
-  "Find hotels in Basel with Basel in its name.",
-  "Can you book the Hilton Basel for me?",
-  "Oh wait, this is too expensive. Please cancel it and book the Hyatt Regency instead.",
-  "My check in dates would be from April 10, 2024 to April 19, 2024.",
-];
-
-function mapZodTypeToOpenAPIType(zodTypeName) {
-
-    console.log(zodTypeName)
-    const typeMap = {
-        'ZodString': 'string',
-        'ZodNumber': 'number',
-        'ZodBoolean': 'boolean',
-        'ZodArray': 'array',
-        'ZodObject': 'object',
-    };
-    return typeMap[zodTypeName] || 'string';
-}
-
-async function runApplication() {
-   
-    const toolboxClient = new ToolboxClient(TOOLBOX_URL); 
-    const toolboxTools = await toolboxClient.loadToolset("my-toolset");
-    
-    const geminiTools = [{
-        functionDeclarations: toolboxTools.map(tool => {
-            
-            const schema = tool.getParamSchema();
-            const properties = {};
-            const required = [];
-
-         
-            for (const [key, param] of Object.entries(schema.shape)) {
-                properties[key] = {
-                        type: mapZodTypeToOpenAPIType(param.constructor.name),
-                        description: param.description || '',
-                    };
-                required.push(key)
-                }
-            
-            return {
-                name: tool.getName(),
-                description: tool.getDescription(),
-                parameters: { type: 'object', properties, required },
-            };
-        })
-    }];
-
-
-    const genAI = new GoogleGenAI({ apiKey: GOOGLE_API_KEY });
-    
-    const chat = genAI.chats.create({
-        model: "gemini-2.5-flash",
-        config: {
-            systemInstruction: prompt,
-            tools: geminiTools,
-        }
-    });
-
-    for (const query of queries) {
-        
-        let currentResult = await chat.sendMessage({ message: query });
-        
-        let finalResponseGiven = false
-        while (!finalResponseGiven) {
-            
-            const response = currentResult;
-            const functionCalls = response.functionCalls || [];
-
-            if (functionCalls.length === 0) {
-                console.log(response.text)
-                finalResponseGiven = true;
-            } else {
-                const toolResponses = [];
-                for (const call of functionCalls) {
-                    const toolName = call.name
-                    const toolToExecute = toolboxTools.find(t => t.getName() === toolName);
-                    
-                    if (toolToExecute) {
-                        try {
-                            const functionResult = await toolToExecute(call.args);
-                            toolResponses.push({
-                                functionResponse: { name: call.name, response: { result: functionResult } }
-                            });
-                        } catch (e) {
-                            console.error(`Error executing tool '${toolName}':`, e);
-                            toolResponses.push({
-                                functionResponse: { name: call.name, response: { error: e.message } }
-                            });
-                        }
-                    }
-                }
-                
-                currentResult = await chat.sendMessage({ message: toolResponses });
-            }
-        }
-        
-    }
-}
-
-runApplication()
-  .catch(console.error)
-  .finally(() => console.log("\nApplication finished."));
-{{< /tab >}}
-
 {{< /tabpane >}}
 
 1. Run your agent, and observe the results:

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

@@ -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.12.0/$OS/toolbox
+    curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/$OS/toolbox
     ```
     <!-- {x-release-please-end} -->
 

docs/en/getting-started/quickstart/shared/cloud_setup.md

@@ -1,20 +0,0 @@
-<!-- This file has been used in local_quickstart.md, local_quickstart_go.md & local_quickstart_js.md -->
-<!-- [START cloud_setup] -->
-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)
-1. Set your project and enable Vertex AI
-
-    ```bash
-    gcloud config set project YOUR_PROJECT_ID
-    gcloud services enable aiplatform.googleapis.com
-    ```
-
-[install-python]: https://wiki.python.org/moin/BeginnersGuide/Download
-[install-pip]: https://pip.pypa.io/en/stable/installation/
-[install-venv]: https://packaging.python.org/en/latest/tutorials/installing-packages/#creating-virtual-environments
-[install-postgres]: https://www.postgresql.org/download/
-<!-- [END cloud_setup] -->

docs/en/getting-started/quickstart/shared/configure_toolbox.md

@@ -1,122 +0,0 @@
-<!-- This file has been used in local_quickstart.md, local_quickstart_go.md & local_quickstart_js.md -->
-<!-- [START configure_toolbox] -->
-In this section, we will download Toolbox, configure our tools in a
-`tools.yaml`, and then run the Toolbox server.
-
-1. Download the latest version of Toolbox as a binary:
-
-    {{< notice tip >}}
-  Select the
-  [correct binary](https://github.com/googleapis/genai-toolbox/releases)
-  corresponding to your OS and CPU architecture.
-    {{< /notice >}}
-    <!-- {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.12.0/$OS/toolbox
-    ```
-    <!-- {x-release-please-end} -->
-
-1. Make the binary executable:
-
-    ```bash
-    chmod +x toolbox
-    ```
-
-1. Write the following into a `tools.yaml` file. Be sure to update any fields
-   such as `user`, `password`, or `database` that you may have customized in the
-   previous step.
-
-    {{< notice tip >}}
-  In practice, use environment variable replacement with the format ${ENV_NAME}
-  instead of hardcoding your secrets into the configuration file.
-    {{< /notice >}}
-
-    ```yaml
-    sources:
-      my-pg-source:
-        kind: postgres
-        host: 127.0.0.1
-        port: 5432
-        database: toolbox_db
-        user: ${USER_NAME}
-        password: ${PASSWORD}
-    tools:
-      search-hotels-by-name:
-        kind: postgres-sql
-        source: my-pg-source
-        description: Search for hotels based on name.
-        parameters:
-          - name: name
-            type: string
-            description: The name of the hotel.
-        statement: SELECT * FROM hotels WHERE name ILIKE '%' || $1 || '%';
-      search-hotels-by-location:
-        kind: postgres-sql
-        source: my-pg-source
-        description: Search for hotels based on location.
-        parameters:
-          - name: location
-            type: string
-            description: The location of the hotel.
-        statement: SELECT * FROM hotels WHERE location ILIKE '%' || $1 || '%';
-      book-hotel:
-        kind: postgres-sql
-        source: my-pg-source
-        description: >-
-           Book a hotel by its ID. If the hotel is successfully booked, returns a NULL, raises an error if not.
-        parameters:
-          - name: hotel_id
-            type: string
-            description: The ID of the hotel to book.
-        statement: UPDATE hotels SET booked = B'1' WHERE id = $1;
-      update-hotel:
-        kind: postgres-sql
-        source: my-pg-source
-        description: >-
-          Update a hotel's check-in and check-out dates by its ID. Returns a message
-          indicating  whether the hotel was successfully updated or not.
-        parameters:
-          - name: hotel_id
-            type: string
-            description: The ID of the hotel to update.
-          - name: checkin_date
-            type: string
-            description: The new check-in date of the hotel.
-          - name: checkout_date
-            type: string
-            description: The new check-out date of the hotel.
-        statement: >-
-          UPDATE hotels SET checkin_date = CAST($2 as date), checkout_date = CAST($3
-          as date) WHERE id = $1;
-      cancel-hotel:
-        kind: postgres-sql
-        source: my-pg-source
-        description: Cancel a hotel by its ID.
-        parameters:
-          - name: hotel_id
-            type: string
-            description: The ID of the hotel to cancel.
-        statement: UPDATE hotels SET booked = B'0' WHERE id = $1;
-   toolsets:
-      my-toolset:
-        - search-hotels-by-name
-        - search-hotels-by-location
-        - book-hotel
-        - update-hotel
-        - cancel-hotel
-    ```
-
-    For more info on tools, check out the `Resources` section of the docs.
-
-1. Run the Toolbox server, pointing to the `tools.yaml` file created earlier:
-
-    ```bash
-    ./toolbox --tools-file "tools.yaml"
-    ```
-
-    {{< notice note >}}
-    Toolbox enables dynamic reloading by default. To disable, use the
-    `--disable-reload` flag.
-    {{< /notice >}}
-<!-- [END configure_toolbox] -->

docs/en/getting-started/quickstart/shared/database_setup.md

@@ -1,119 +0,0 @@
-<!-- This file has been used in local_quickstart.md, local_quickstart_go.md & local_quickstart_js.md -->
-<!-- [START database_setup] -->
-In this section, we will create a database, insert some data that needs to be
-accessed by our agent, and create a database user for Toolbox to connect with.
-
-1. Connect to postgres using the `psql` command:
-
-    ```bash
-    psql -h 127.0.0.1 -U postgres
-    ```
-
-    Here, `postgres` denotes the default postgres superuser.
-
-    {{< notice info >}}
-
-#### **Having trouble connecting?**
-
-* **Password Prompt:** If you are prompted for a password for the `postgres`
-  user and do not know it (or a blank password doesn't work), your PostgreSQL
-  installation might require a password or a different authentication method.
-* **`FATAL: role "postgres" does not exist`:** This error means the default
-  `postgres` superuser role isn't available under that name on your system.
-* **`Connection refused`:** Ensure your PostgreSQL server is actually running.
-  You can typically check with `sudo systemctl status postgresql` and start it
-  with `sudo systemctl start postgresql` on Linux systems.
-
-<br/>
-
-#### **Common Solution**
-
-For password issues or if the `postgres` role seems inaccessible directly, try
-switching to the `postgres` operating system user first. This user often has
-permission to connect without a password for local connections (this is called
-peer authentication).
-
-```bash
-sudo -i -u postgres
-psql -h 127.0.0.1
-```
-
-Once you are in the `psql` shell using this method, you can proceed with the
-database creation steps below. Afterwards, type `\q` to exit `psql`, and then
-`exit` to return to your normal user shell.
-
-If desired, once connected to `psql` as the `postgres` OS user, you can set a
-password for the `postgres` *database* user using: `ALTER USER postgres WITH
-PASSWORD 'your_chosen_password';`. This would allow direct connection with `-U
-postgres` and a password next time.
-    {{< /notice >}}
-
-1. Create a new database and a new user:
-
-    {{< notice tip >}}
-  For a real application, it's best to follow the principle of least permission
-  and only grant the privileges your application needs.
-    {{< /notice >}}
-
-    ```sql
-      CREATE USER toolbox_user WITH PASSWORD 'my-password';
-
-      CREATE DATABASE toolbox_db;
-      GRANT ALL PRIVILEGES ON DATABASE toolbox_db TO toolbox_user;
-
-      ALTER DATABASE toolbox_db OWNER TO toolbox_user;
-    ```
-
-1. End the database session:
-
-    ```bash
-    \q
-    ```
-
-    (If you used `sudo -i -u postgres` and then `psql`, remember you might also
-    need to type `exit` after `\q` to leave the `postgres` user's shell
-    session.)
-
-1. Connect to your database with your new user:
-
-    ```bash
-    psql -h 127.0.0.1 -U toolbox_user -d toolbox_db
-    ```
-
-1. Create a table using the following command:
-
-    ```sql
-    CREATE TABLE hotels(
-      id            INTEGER NOT NULL PRIMARY KEY,
-      name          VARCHAR NOT NULL,
-      location      VARCHAR NOT NULL,
-      price_tier    VARCHAR NOT NULL,
-      checkin_date  DATE    NOT NULL,
-      checkout_date DATE    NOT NULL,
-      booked        BIT     NOT NULL
-    );
-    ```
-
-1. Insert data into the table.
-
-    ```sql
-    INSERT INTO hotels(id, name, location, price_tier, checkin_date, checkout_date, booked)
-    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'),
-      (4, 'Radisson Blu Lucerne', 'Lucerne', 'Midscale', '2024-04-24', '2024-04-05', B'0'),
-      (5, 'Best Western Bern', 'Bern', 'Upper Midscale', '2024-04-23', '2024-04-01', B'0'),
-      (6, 'InterContinental Geneva', 'Geneva', 'Luxury', '2024-04-23', '2024-04-28', B'0'),
-      (7, 'Sheraton Zurich', 'Zurich', 'Upper Upscale', '2024-04-27', '2024-04-02', B'0'),
-      (8, 'Holiday Inn Basel', 'Basel', 'Upper Midscale', '2024-04-24', '2024-04-09', B'0'),
-      (9, 'Courtyard Zurich', 'Zurich', 'Upscale', '2024-04-03', '2024-04-13', B'0'),
-      (10, 'Comfort Inn Bern', 'Bern', 'Midscale', '2024-04-04', '2024-04-16', B'0');
-    ```
-
-1. End the database session:
-
-    ```bash
-    \q
-    ```
-<!-- [END database_setup] -->

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

@@ -62,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.12.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.12.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.12.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.12.0/windows/amd64/toolbox
+curl -O https://storage.googleapis.com/genai-toolbox/v0.11.0/windows/amd64/toolbox
 {{< /tab >}}
 {{< /tabpane >}}
     <!-- {x-release-please-end} -->

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

@@ -11,7 +11,6 @@ an open protocol for connecting Large Language Models (LLMs) to data sources
 like Postgres. This guide covers how to use [MCP Toolbox for Databases][toolbox]
 to expose your developer assistant tools to a Looker instance:
 
-* [Gemini-CLI][gemini-cli]
 * [Cursor][cursor]
 * [Windsurf][windsurf] (Codium)
 * [Visual Studio Code][vscode] (Copilot)
@@ -20,7 +19,6 @@ to expose your developer assistant tools to a Looker instance:
 * [Claude code][claudecode]
 
 [toolbox]: https://github.com/googleapis/genai-toolbox
-[gemini-cli]: #configure-your-mcp-client
 [cursor]: #configure-your-mcp-client
 [windsurf]: #configure-your-mcp-client
 [vscode]: #configure-your-mcp-client
@@ -48,19 +46,19 @@ to expose your developer assistant tools to a Looker instance:
    <!-- {x-release-please-start-version} -->
 {{< tabpane persist=header >}}
 {{< tab header="linux/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.12.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.12.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.12.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.12.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} -->
@@ -80,36 +78,6 @@ curl -O https://storage.googleapis.com/genai-toolbox/v0.12.0/windows/amd64/toolb
 ## Configure your MCP Client
 
 {{< tabpane text=true >}}
-{{% tab header="Gemini-CLI" lang="en" %}}
-
-1. Install [Gemini-CLI](https://github.com/google-gemini/gemini-cli#install-globally-with-npm).
-1. Create a directory `.gemini` in your home directory if it doesn't exist.
-1. Create the file `.gemini/settings.json` if it doesn't exist.
-1. Add the following configuration, or add the mcpServers stanza if you already
-   have a `settings.json` with content. Replace the path to the toolbox
-   executable and the environment variables with your values, and save:
-
-    ```json
-    {
-      "mcpServers": {
-        "looker-toolbox": {
-          "command": "./PATH/TO/toolbox",
-          "args": ["--stdio", "--prebuilt", "looker"],
-          "env": {
-            "LOOKER_BASE_URL": "https://looker.example.com",
-            "LOOKER_CLIENT_ID": "",
-            "LOOKER_CLIENT_SECRET": "",
-            "LOOKER_VERIFY_SSL": "true"
-          }
-        }
-      }
-    }
-    ```
-
-1. Start Gemini-CLI with the `gemini` command and use the command `/mcp` to see
-   the configured MCP tools.
-{{% /tab %}}
-
 {{% tab header="Claude code" lang="en" %}}
 
 1. Install [Claude
@@ -295,15 +263,11 @@ 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 and return the data
+1. **query**: Run a query
 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
-1. **get_dashboards**: Return the saved dashboards that match a title or description
-1. **make_dashboard**: Create a saved dashboard in Looker and return the URL
-1. **add_dashboard_element**: Add a tile to a dashboard
 
 {{< 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

@@ -1,289 +0,0 @@
----
-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.12.0/linux/amd64/toolbox
-{{< /tab >}}
-
-{{< tab header="darwin/arm64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.12.0/darwin/arm64/toolbox
-{{< /tab >}}
-
-{{< tab header="darwin/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.12.0/darwin/amd64/toolbox
-{{< /tab >}}
-
-{{< tab header="windows/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.12.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

@@ -1,287 +0,0 @@
----
-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.12.0/linux/amd64/toolbox
-{{< /tab >}}
-
-{{< tab header="darwin/arm64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.12.0/darwin/arm64/toolbox
-{{< /tab >}}
-
-{{< tab header="darwin/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.12.0/darwin/amd64/toolbox
-{{< /tab >}}
-
-{{< tab header="windows/amd64" lang="bash" >}}
-curl -O https://storage.googleapis.com/genai-toolbox/v0.12.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.12.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.12.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.12.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.12.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/deploy_docker.md

@@ -75,7 +75,7 @@ networks:
 
 {{< notice tip >}}
 
-You can use this setup to quickly set up Toolbox + Postgres to follow along in our
+You can use this setup quickly set up Toolbox + Postgres to follow along in our
 [Quickstart](../getting-started/local_quickstart.md)
 
 {{< /notice >}}

docs/en/how-to/deploy_gke.md

@@ -60,8 +60,8 @@ description: >
     gcloud iam service-accounts create $SA_NAME
     ```
 
-1. Grant any IAM roles necessary to the IAM service account. Each source has a
-    list of necessary IAM permissions listed on its page. The example below is
+1. Grant any IAM roles necessary to the IAM service account. Each source have a
+    list of necessary IAM permissions listed on it's page. The example below is
     for cloud sql postgres source:
 
     ```bash

docs/en/how-to/deploy_toolbox.md

@@ -103,14 +103,6 @@ section.
     ```bash
     export IMAGE=us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:latest
     ```
-{{< notice note >}}  
-**The `$PORT` Environment Variable**  
-Google Cloud Run dictates the port your application must listen on by setting the
-`$PORT` environment variable inside your container. This value defaults to
-**8080**. Your application's `--port` argument **must** be set to listen on this
-port. If there is a mismatch, the container will fail to start and the
-deployment will time out.  
-{{< /notice >}}
 
 1. Deploy Toolbox to Cloud Run using the following command:
 
@@ -149,7 +141,7 @@ You can connect to Toolbox Cloud Run instances directly through the SDK.
 
 1. (Only for local runs) Set up [Application Default
    Credentials](https://cloud.google.com/docs/authentication/set-up-adc-local-dev-environment)
-   for the principal you set up the `Cloud Run Invoker` role access to.
+   for the principle you set up the `Cloud Run Invoker` role access to.
 
 1. Run the following to retrieve a non-deterministic URL for the cloud run service:
 
@@ -159,68 +151,18 @@ You can connect to Toolbox Cloud Run instances directly through the SDK.
 
 1. Import and initialize the toolbox client with the URL retrieved above:
 
-    {{< tabpane persist=header >}}
-{{< tab header="Python" lang="python" >}}
-from toolbox_core import ToolboxClient, auth_methods
+    ```python
+    from toolbox_core import ToolboxClient, auth_methods
 
-# Replace with the Cloud Run service URL generated in the previous step.
-URL = "https://cloud-run-url.app"
+    # Replace with the Cloud Run service URL generated in the previous step.
+    URL = "https://cloud-run-url.app"
 
-auth_token_provider = auth_methods.aget_google_id_token(URL) # can also use sync method
+    auth_token_provider = auth_methods.aget_google_id_token(URL) # can also use sync method
 
-async with ToolboxClient(
-    URL,
-    client_headers={"Authorization": auth_token_provider},
-) as toolbox:
-{{< /tab >}}
-{{< tab header="Javascript" lang="javascript" >}}
-import { ToolboxClient } from '@toolbox-sdk/core';
-import {getGoogleIdToken} from '@toolbox-sdk/core/auth'
-
-// Replace with the Cloud Run service URL generated in the previous step.
-const URL = 'http://127.0.0.1:5000';
-const authTokenProvider = () => getGoogleIdToken(URL);
-
-const client = new ToolboxClient(URL, null, {"Authorization": authTokenProvider});
-{{< /tab >}}
-{{< tab header="Go" lang="go" >}}
-import "github.com/googleapis/mcp-toolbox-sdk-go/core"
-
-func main() {
-    // Replace with the Cloud Run service URL generated in the previous step.
-    URL := "http://127.0.0.1:5000"
-    auth_token_provider, err := core.GetGoogleIDToken(ctx, URL)
-    if err != nil {
-        log.Fatalf("Failed to fetch token %v", err)
-    }
-    toolboxClient, err := core.NewToolboxClient(
+    async with ToolboxClient(
         URL,
-        core.WithClientHeaderString("Authorization", auth_token_provider))
-    if err != nil {
-        log.Fatalf("Failed to create Toolbox client: %v", err)
-    }
-}
-{{< /tab >}}
-{{< /tabpane >}}
-
+        client_headers={"Authorization": auth_token_provider},
+    ) as toolbox:
+    ```
 
 Now, you can use this client to connect to the deployed Cloud Run instance!
-
-## Troubleshooting
-
-{{< notice note >}}  
-For any deployment or runtime error, the best first step is to check the logs for your service in the Google Cloud Console's Cloud Run section. They often contain the specific error message needed to diagnose the problem.  
-{{< /notice >}}
-
-* **Deployment Fails with "Container failed to start":** This is almost always
-    caused by a port mismatch. Ensure your container's `--port` argument is set to
-    `8080` to match the `$PORT` environment variable provided by Cloud Run.
-
-* **Client Receives Permission Denied Error (401 or 403):** If your client application (e.g., your local SDK) gets a `401 Unauthorized` or `403 Forbidden` error when trying to call your Cloud Run service, it means the client is not properly authenticated as an invoker.
-    * Ensure the user or service account calling the service has the **Cloud Run Invoker** (`roles/run.invoker`) IAM role.
-    * If running locally, make sure your Application Default Credentials are set up correctly by running `gcloud auth application-default login`.
-
-* **Service Fails to Access Secrets (in logs):** If your application starts but the logs show errors like "permission denied" when trying to access Secret Manager, it means the Toolbox service account is missing permissions.
-    * Ensure the `toolbox-identity` service account has the **Secret Manager Secret Accessor** (`roles/secretmanager.secretAccessor`) IAM role.
-
-

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

@@ -36,10 +36,10 @@ with the tool name, description, and available parameters.
 ### Invoking a Tool
 
 1. Click on a Tool
-1. Enter appropriate parameters in each parameter field
-1. Click "Run Tool"
-1. Done! Your results will appear in the response field
-1. (Optional) Uncheck "Prettify JSON" to format the response as plain text
+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)
 
@@ -78,16 +78,13 @@ button and modal described above. The key should be the name of your AuthService
 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]()
-1. The auth parameter's text field is greyed out. This is because it cannot be entered manually and will
+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
-1. To update request headers with the token, select "Edit Headers"
-1. (Optional) If you wish to manually edit the header, checkout the dropdown "How to extract Google OAuth ID Token manually" for guidance on retrieving ID token
-1. To edit the header automatically, click the "Auto Setup" button that is associated with your Auth Profile
-1. Enter the Client ID defined in your tools configuration file
-1. Click "Continue"
-1. Click "Sign in With Google" and login with your associated google account. This should automatically populate the header text area with your token
-1. Click "Save"
-1. Click "Run Tool"
+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
 {

docs/en/reference/_index.md

@@ -1,8 +0,0 @@
----
-title: "Reference"
-type: docs
-weight: 7
-description: >
-  This section contains reference documentation.
----
-

docs/en/reference/cli.md

@@ -1,75 +0,0 @@
----
-title: "CLI"
-type: docs
-weight: 1
-description: >
-  This page describes the `toolbox` command-line options.
----
-
-## Reference
-
-| Flag (Short) | Flag (Long) | Description | Default |
-|---|---|---|---|
-| `-a` | `--address` | Address of the interface the server will listen on. | `127.0.0.1` |
-| | `--disable-reload` | Disables dynamic reloading of tools file. | |
-| `-h` | `--help` | help for toolbox | |
-| | `--log-level` | Specify the minimum level logged. Allowed: 'DEBUG', 'INFO', 'WARN', 'ERROR'. | `info` |
-| | `--logging-format` | Specify logging format to use. Allowed: 'standard' or 'JSON'. | `standard` |
-| `-p` | `--port` | Port the server will listen on. | `5000` |
-| | `--prebuilt` | Use a prebuilt tool configuration by source type. Cannot be used with --tools-file. See [Prebuilt Tools Reference](prebuilt-tools.md) for allowed values. | |
-| | `--stdio` | Listens via MCP STDIO instead of acting as a remote HTTP server. | |
-| | `--telemetry-gcp` | Enable exporting directly to Google Cloud Monitoring. | |
-| | `--telemetry-otlp` | Enable exporting using OpenTelemetry Protocol (OTLP) to the specified endpoint (e.g. 'http://127.0.0.1:4318') | |
-| | `--telemetry-service-name` | Sets the value of the service.name resource attribute for telemetry data. | `toolbox` |
-| | `--tools-file` | File path specifying the tool configuration. Cannot be used with --prebuilt, --tools-files, or --tools-folder. | |
-| | `--tools-files` | Multiple file paths specifying tool configurations. Files will be merged. Cannot be used with --prebuilt, --tools-file, or --tools-folder. | |
-| | `--tools-folder` | Directory path containing YAML tool configuration files. All .yaml and .yml files in the directory will be loaded and merged. Cannot be used with --prebuilt, --tools-file, or --tools-files. | |
-| | `--ui` | Launches the Toolbox UI web server. | |
-| `-v` | `--version` | version for toolbox | |
-
-## Examples
-
-### Transport Configuration
-
-**Server Settings:**
-- `--address`, `-a`: Server listening address (default: "127.0.0.1")
-- `--port`, `-p`: Server listening port (default: 5000)
-
-**STDIO:**
-- `--stdio`: Run in MCP STDIO mode instead of HTTP server
-
-#### Usage Examples
-
-```bash
-# Basic server with custom port configuration
-./toolbox --tools-file "tools.yaml" --port 8080
-```
-
-### Tool Configuration Sources
-
-The CLI supports multiple mutually exclusive ways to specify tool configurations:
-
-**Single File:** (default)
-- `--tools-file`: Path to a single YAML configuration file (default: `tools.yaml`)
-
-**Multiple Files:**
-- `--tools-files`: Comma-separated list of YAML files to merge
-
-**Directory:**
-- `--tools-folder`: Directory containing YAML files to load and merge
-
-**Prebuilt Configurations:**
-- `--prebuilt`: Use predefined configurations for specific database types (e.g., 'bigquery', 'postgres', 'spanner'). See [Prebuilt Tools Reference](prebuilt-tools.md) for allowed values.
-
-{{< notice tip >}}
-The CLI enforces mutual exclusivity between configuration source flags, preventing simultaneous use of `--prebuilt` with file-based options, and ensuring only one of `--tools-file`, `--tools-files`, or `--tools-folder` is used at a time.
-{{< /notice >}}
-
-### Hot Reload
-
-Toolbox enables dynamic reloading by default. To disable, use the
-`--disable-reload` flag.
-
-### 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/toolbox-ui/index.md).

docs/en/reference/prebuilt-tools.md

@@ -1,260 +0,0 @@
----
-title: "Prebuilt Tools"
-type: docs
-weight: 1
-description: >
-    This page lists all the prebuilt tools available.
----
-
-Prebuilt tools are reusable, pre-packaged toolsets that are designed to extend the capabilities of agents. These tools are built to be generic and adaptable, allowing developers to interact with and take action on databases.
-
-See guides, [Connect from your IDE](../how-to/connect-ide/_index.md), for details on how to connect your AI tools (IDEs) to databases via Toolbox and MCP.
-
-## AlloyDB Postgres
-
-*   `--prebuilt` value: `alloydb-postgres`
-*   **Environment Variables:**
-    *   `ALLOYDB_POSTGRES_PROJECT`: The GCP project ID.
-    *   `ALLOYDB_POSTGRES_REGION`: The region of your AlloyDB instance.
-    *   `ALLOYDB_POSTGRES_CLUSTER`: The ID of your AlloyDB cluster.
-    *   `ALLOYDB_POSTGRES_INSTANCE`: The ID of your AlloyDB instance.
-    *   `ALLOYDB_POSTGRES_DATABASE`: The name of the database to connect to.
-    *   `ALLOYDB_POSTGRES_USER`: The database username.
-    *   `ALLOYDB_POSTGRES_PASSWORD`: The password for the database user.
-*   **Permissions:**
-    *   **AlloyDB Client** (`roles/alloydb.client`) to connect to the instance.
-    *   Database-level permissions (e.g., `SELECT`, `INSERT`) are required to execute queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## AlloyDB Postgres Admin
-
-* `--prebuilt` value: `alloydb-postgres-admin`
-*   **Environment Variables:**
-    *   `API_KEY`: Your API key for the AlloyDB API.
-*   **Permissions:**
-    *   **AlloyDB Admin** (`roles/alloydb.admin`) IAM role is required on the project.
-*   **Tools:**
-    *   `alloydb-create-cluster`: Creates a new AlloyDB cluster.
-    *   `alloydb-operations-get`: Polls the operations API to track the status of long-running operations.
-    *   `alloydb-create-instance`: Creates a new AlloyDB instance within a cluster.
-    *   `alloydb-list-clusters`: Lists all AlloyDB clusters in a project.
-    *   `alloydb-list-instances`: Lists all instances within an AlloyDB cluster.
-    *   `alloydb-list-users`: Lists all database users within an AlloyDB cluster.
-    *   `alloydb-create-user`: Creates a new database user in an AlloyDB cluster.
-
-## BigQuery
-
-*   `--prebuilt` value: `bigquery`
-*   **Environment Variables:**
-    *   `BIGQUERY_PROJECT`: The GCP project ID.
-*   **Permissions:**
-    *   **BigQuery User** (`roles/bigquery.user`) to execute queries and view metadata.
-    *   **BigQuery Metadata Viewer** (`roles/bigquery.metadataViewer`) to view all datasets.
-    *   **BigQuery Data Editor** (`roles/bigquery.dataEditor`) to create or modify datasets and tables.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL statement.
-    *   `get_dataset_info`: Gets dataset metadata.
-    *   `get_table_info`: Gets table metadata.
-    *   `list_dataset_ids`: Lists datasets.
-    *   `list_table_ids`: Lists tables.
-
-## Cloud SQL for MySQL
-
-*   `--prebuilt` value: `cloud-sql-mysql`
-*   **Environment Variables:**
-    *   `CLOUD_SQL_MYSQL_PROJECT`: The GCP project ID.
-    *   `CLOUD_SQL_MYSQL_REGION`: The region of your Cloud SQL instance.
-    *   `CLOUD_SQL_MYSQL_INSTANCE`: The ID of your Cloud SQL instance.
-    *   `CLOUD_SQL_MYSQL_DATABASE`: The name of the database to connect to.
-    *   `CLOUD_SQL_MYSQL_USER`: The database username.
-    *   `CLOUD_SQL_MYSQL_PASSWORD`: The password for the database user.
-*   **Permissions:**
-    *   **Cloud SQL Client** (`roles/cloudsql.client`) to connect to the instance.
-    *   Database-level permissions (e.g., `SELECT`, `INSERT`) are required to execute queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## Cloud SQL for PostgreSQL
-
-*   `--prebuilt` value: `cloud-sql-postgres`
-*   **Environment Variables:**
-    *   `CLOUD_SQL_POSTGRES_PROJECT`: The GCP project ID.
-    *   `CLOUD_SQL_POSTGRES_REGION`: The region of your Cloud SQL instance.
-    *   `CLOUD_SQL_POSTGRES_INSTANCE`: The ID of your Cloud SQL instance.
-    *   `CLOUD_SQL_POSTGRES_DATABASE`: The name of the database to connect to.
-    *   `CLOUD_SQL_POSTGRES_USER`: The database username.
-    *   `CLOUD_SQL_POSTGRES_PASSWORD`: The password for the database user.
-*   **Permissions:**
-    *   **Cloud SQL Client** (`roles/cloudsql.client`) to connect to the instance.
-    *   Database-level permissions (e.g., `SELECT`, `INSERT`) are required to execute queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## Cloud SQL for SQL Server
-
-*   `--prebuilt` value: `cloud-sql-mssql`
-*   **Environment Variables:**
-    *   `CLOUD_SQL_MSSQL_PROJECT`: The GCP project ID.
-    *   `CLOUD_SQL_MSSQL_REGION`: The region of your Cloud SQL instance.
-    *   `CLOUD_SQL_MSSQL_INSTANCE`: The ID of your Cloud SQL instance.
-    *   `CLOUD_SQL_MSSQL_DATABASE`: The name of the database to connect to.
-    *   `CLOUD_SQL_MSSQL_IP_ADDRESS`: The IP address of the Cloud SQL instance.
-    *   `CLOUD_SQL_MSSQL_USER`: The database username.
-    *   `CLOUD_SQL_MSSQL_PASSWORD`: The password for the database user.
-*   **Permissions:**
-    *   **Cloud SQL Client** (`roles/cloudsql.client`) to connect to the instance.
-    *   Database-level permissions (e.g., `SELECT`, `INSERT`) are required to execute queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## Dataplex
-
-*   `--prebuilt` value: `dataplex`
-*   **Environment Variables:**
-    *   `DATAPLEX_PROJECT`: The GCP project ID.
-*   **Permissions:**
-    *   **Dataplex Reader** (`roles/dataplex.viewer`) to search and look up entries.
-    *   **Dataplex Editor** (`roles/dataplex.editor`) to modify entries.
-*   **Tools:**
-    *   `dataplex_search_entries`: Searches for entries in Dataplex Catalog.
-    *   `dataplex_lookup_entry`: Retrieves a specific entry from Dataplex Catalog.
-    *   `dataplex_search_aspect_types`: Finds aspect types relevant to the query.
-
-## Firestore
-
-*   `--prebuilt` value: `firestore`
-*   **Environment Variables:**
-    *   `FIRESTORE_PROJECT`: The GCP project ID.
-    *   `FIRESTORE_DATABASE`: The Firestore database ID.
-*   **Permissions:**
-    *   **Cloud Datastore User** (`roles/datastore.user`) to get documents, list collections, and query collections.
-    *   **Firebase Rules Viewer** (`roles/firebaserules.viewer`) to get and validate Firestore rules.
-*   **Tools:**
-    *   `firestore-get-documents`: Gets multiple documents from Firestore by their paths.
-    *   `firestore-list-collections`: Lists Firestore collections for a given parent path.
-    *   `firestore-delete-documents`: Deletes multiple documents from Firestore.
-    *   `firestore-query-collection`: Retrieves one or more Firestore documents from a collection.
-    *   `firestore-get-rules`: Retrieves the active Firestore security rules.
-    *   `firestore-validate-rules`: Checks the provided Firestore Rules source for syntax and validation errors.
-
-## Looker
-
-*   `--prebuilt` value: `looker`
-*   **Environment Variables:**
-    *   `LOOKER_BASE_URL`: The URL of your Looker instance.
-    *   `LOOKER_CLIENT_ID`: The client ID for the Looker API.
-    *   `LOOKER_CLIENT_SECRET`: The client secret for the Looker API.
-    *   `LOOKER_VERIFY_SSL`: Whether to verify SSL certificates.
-*   **Permissions:**
-    *   A Looker account with permissions to access the desired models, explores, and data is required.
-*   **Tools:**
-    *   `get_models`: Retrieves the list of LookML models.
-    *   `get_explores`: Retrieves the list of explores in a model.
-    *   `get_dimensions`: Retrieves the list of dimensions in an explore.
-    *   `get_measures`: Retrieves the list of measures in an explore.
-    *   `get_filters`: Retrieves the list of filters in an explore.
-    *   `get_parameters`: Retrieves the list of parameters in an explore.
-    *   `query`: Runs a query against the LookML model.
-    *   `query_sql`: Generates the SQL for a query.
-    *   `query_url`: Generates a URL for a query in Looker.
-    *   `get_looks`: Searches for saved looks.
-    *   `run_look`: Runs the query associated with a look.
-    *   `make_look`: Creates a new look.
-    *   `get_dashboards`: Searches for saved dashboards.
-    *   `make_dashboard`: Creates a new dashboard.
-    *   `add_dashboard_element`: Adds a tile to a dashboard.
-
-## Microsoft SQL Server
-
-*   `--prebuilt` value: `mssql`
-*   **Environment Variables:**
-    *   `MSSQL_HOST`: The hostname or IP address of the SQL Server instance.
-    *   `MSSQL_PORT`: The port number for the SQL Server instance.
-    *   `MSSQL_DATABASE`: The name of the database to connect to.
-    *   `MSSQL_USER`: The database username.
-    *   `MSSQL_PASSWORD`: The password for the database user.
-*   **Permissions:**
-    *   Database-level permissions (e.g., `SELECT`, `INSERT`) are required to execute queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## MySQL
-
-*   `--prebuilt` value: `mysql`
-*   **Environment Variables:**
-    *   `MYSQL_HOST`: The hostname or IP address of the MySQL server.
-    *   `MYSQL_PORT`: The port number for the MySQL server.
-    *   `MYSQL_DATABASE`: The name of the database to connect to.
-    *   `MYSQL_USER`: The database username.
-    *   `MYSQL_PASSWORD`: The password for the database user.
-*   **Permissions:**
-    *   Database-level permissions (e.g., `SELECT`, `INSERT`) are required to execute queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## OceanBase
-
-*   `--prebuilt` value: `oceanbase`
-*   **Environment Variables:**
-    *   `OCEANBASE_HOST`: The hostname or IP address of the OceanBase server.
-    *   `OCEANBASE_PORT`: The port number for the OceanBase server.
-    *   `OCEANBASE_DATABASE`: The name of the database to connect to.
-    *   `OCEANBASE_USER`: The database username.
-    *   `OCEANBASE_PASSWORD`: The password for the database user.
-*   **Permissions:**
-    *   Database-level permissions (e.g., `SELECT`, `INSERT`) are required to execute queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## PostgreSQL
-
-*   `--prebuilt` value: `postgres`
-*   **Environment Variables:**
-    *   `POSTGRES_HOST`: The hostname or IP address of the PostgreSQL server.
-    *   `POSTGRES_PORT`: The port number for the PostgreSQL server.
-    *   `POSTGRES_DATABASE`: The name of the database to connect to.
-    *   `POSTGRES_USER`: The database username.
-    *   `POSTGRES_PASSWORD`: The password for the database user.
-*   **Permissions:**
-    *   Database-level permissions (e.g., `SELECT`, `INSERT`) are required to execute queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## Spanner (GoogleSQL dialect)
-
-*   `--prebuilt` value: `spanner`
-*   **Environment Variables:**
-    *   `SPANNER_PROJECT`: The GCP project ID.
-    *   `SPANNER_INSTANCE`: The Spanner instance ID.
-    *   `SPANNER_DATABASE`: The Spanner database ID.
-*   **Permissions:**
-    *   **Cloud Spanner Database Reader** (`roles/spanner.databaseReader`) to execute DQL queries and list tables.
-    *   **Cloud Spanner Database User** (`roles/spanner.databaseUser`) to execute DML queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a DML SQL query.
-    *   `execute_sql_dql`: Executes a DQL SQL query.
-    *   `list_tables`: Lists tables in the database.
-
-## Spanner (PostgreSQL dialect)
-
-*   `--prebuilt` value: `spanner-postgres`
-*   **Environment Variables:**
-    *   `SPANNER_PROJECT`: The GCP project ID.
-    *   `SPANNER_INSTANCE`: The Spanner instance ID.
-    *   `SPANNER_DATABASE`: The Spanner database ID.
-*   **Permissions:**
-    *   **Cloud Spanner Database Reader** (`roles/spanner.databaseReader`) to execute DQL queries and list tables.
-    *   **Cloud Spanner Database User** (`roles/spanner.databaseUser`) to execute DML queries.
-*   **Tools:**
-    *   `execute_sql`: Executes a DML SQL query using the PostgreSQL interface for Spanner.
-    *   `execute_sql_dql`: Executes a DQL SQL query using the PostgreSQL interface for Spanner.
-    *   `list_tables`: Lists tables in the database.

docs/en/resources/authServices/_index.md

@@ -68,10 +68,6 @@ parameter when loading tools, or the `add_auth_token_getter`() /
 
 ### Specifying tokens during load
 
-#### Python
-
-Use the [Python SDK](https://github.com/googleapis/mcp-toolbox-sdk-python/tree/main).
-
 {{< tabpane persist=header >}}
 {{< tab header="Core" lang="Python" >}}
 import asyncio
@@ -139,69 +135,8 @@ if **name** == "**main**":
     asyncio.run(main()){{< /tab >}}
 {{< /tabpane >}}
 
-#### Javascript/Typescript
-
-Use the [JS SDK](https://github.com/googleapis/mcp-toolbox-sdk-js/tree/main).
-
-```javascript
-import { ToolboxClient } from '@toolbox-sdk/core';
-
-async function getAuthToken() {
-    // ... Logic to retrieve ID token (e.g., from local storage, OAuth flow)
-    // This example just returns a placeholder. Replace with your actual token retrieval.
-    return "YOUR_ID_TOKEN" // Placeholder
-}
-
-const URL = 'http://127.0.0.1:5000';
-let client = new ToolboxClient(URL);
-const authTool = await client.loadTool("my-tool", {"my_auth_app_1": getAuthToken});
-const result = await authTool({param:"value"});
-console.log(result);
-print(result)
-```
-
-#### Go
-
-Use the [Go SDK](https://github.com/googleapis/mcp-toolbox-sdk-go/tree/main).
-
-```go
-import "github.com/googleapis/mcp-toolbox-sdk-go/core"
-import "fmt"
-
-func getAuthToken() string {
-	// ... Logic to retrieve ID token (e.g., from local storage, OAuth flow)
-	// This example just returns a placeholder. Replace with your actual token retrieval.
-	return "YOUR_ID_TOKEN" // Placeholder
-}
-
-func main() {
-	URL := 'http://127.0.0.1:5000'
-	client, err := core.NewToolboxClient(URL)
-	if err != nil {
-		log.Fatalf("Failed to create Toolbox client: %v", err)
-  	}
-	dynamicTokenSource := core.NewCustomTokenSource(getAuthToken)
-	authTool, err := client.LoadTool(
-		"my-tool",
-		ctx,
-		core.WithAuthTokenSource("my_auth_app_1", dynamicTokenSource))
-	if err != nil {
-		log.Fatalf("Failed to load tool: %v", err)
-	}
-	inputs := map[string]any{"param": "value"}
-	result, err := authTool.Invoke(ctx, inputs)
-	if err != nil {
-		log.Fatalf("Failed to invoke tool: %v", err)
-	}
-	fmt.Println(result)
-}
-```
-
 ### Specifying tokens for existing tools
 
-#### Python
-Use the [Python SDK](https://github.com/googleapis/mcp-toolbox-sdk-python/tree/main).
-
 {{< tabpane persist=header >}}
 {{< tab header="Core" lang="Python" >}}
 tools = await toolbox.load_toolset()
@@ -247,57 +182,4 @@ authorized_tool = tools[0].add_auth_token_getters({
 {{< /tab >}}
 {{< /tabpane >}}
 
-#### Javascript/Typescript
-
-Use the [JS SDK](https://github.com/googleapis/mcp-toolbox-sdk-js/tree/main).
-
-```javascript
-const URL = 'http://127.0.0.1:5000';
-let client = new ToolboxClient(URL);
-let tool = await client.loadTool("my-tool")
-
-// for a single token
-const authorizedTool = tool.addAuthTokenGetter("my_auth", get_auth_token)
-
-// OR, if multiple tokens are needed
-const multiAuthTool = tool.addAuthTokenGetters({
-    "my_auth_1": getAuthToken1,
-    "my_auth_2": getAuthToken2,
-})
-
-```
-
-#### Go
-
-Use the [Go SDK](https://github.com/googleapis/mcp-toolbox-sdk-go/tree/main).
-
-```go
-import "github.com/googleapis/mcp-toolbox-sdk-go/core"
-
-func main() {
-	URL := 'http://127.0.0.1:5000'
-	client, err := core.NewToolboxClient(URL)
-	if err != nil {
-		log.Fatalf("Failed to create Toolbox client: %v", err)
-	}
-	tool, err := client.LoadTool("my-tool", ctx))
-	if err != nil {
-		log.Fatalf("Failed to load tool: %v", err)
-	}
-	dynamicTokenSource1 := core.NewCustomTokenSource(getAuthToken1)
-	dynamicTokenSource2 := core.NewCustomTokenSource(getAuthToken1)
-
-	// For a single token
-	authTool, err := tool.ToolFrom(
-		core.WithAuthTokenSource("my-auth", dynamicTokenSource),
-	)
-
-	// OR, if multiple tokens are needed
-	authTool, err := tool.ToolFrom(
-		core.WithAuthTokenSource("my-auth_1", dynamicTokenSource1),
-		core.WithAuthTokenSource("my-auth_2", dynamicTokenSource2),
-	)
-}
-```
-
 ## Kinds of Auth Services

docs/en/resources/authServices/google.md

@@ -33,7 +33,7 @@ ID.
 When using [Authenticated Parameters][auth-params], any [claim provided by the
 id-token][provided-claims] can be used for the parameter.
 
-[auth-params]: ../tools/#authenticated-parameters
+[auth-params]: ../tools/#authenticated-phugarameters
 [provided-claims]:
     https://developers.google.com/identity/openid-connect/openid-connect#obtaininguserprofileinformation
 

docs/en/resources/sources/couchbase.md

@@ -22,17 +22,13 @@ allowing tools to execute SQL queries against it.
 sources:
     my-couchbase-instance:
         kind: couchbase
-        connectionString: couchbase://localhost
+        connectionString: couchbase://localhost:8091
         bucket: travel-sample
         scope: inventory
         username: Administrator
         password: password
 ```
 
-{{< notice note >}}
-For more details about alternate addresses and custom ports refer to [Managing Connections](https://docs.couchbase.com/java-sdk/current/howtos/managing-connections.html).
-{{< /notice >}}
-
 ## Reference
 
 | **field**            | **type** | **required** | **description**                                         |

docs/en/resources/sources/dataplex.md

@@ -218,45 +218,22 @@ Search syntax supports the following qualifiers:
 - "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. It supports same syntax as `name` predicate.
+- "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.
-
-### Aspect Search
-To search for entries based on their attached aspects, use the following query syntax.
-
-aspect:x	Matches x as a substring of the full path to the aspect type of an aspect that is attached to the entry, in the format projectid.location.ASPECT_TYPE_ID
-aspect=x	Matches x as the full path to the aspect type of an aspect that is attached to the entry, in the format projectid.location.ASPECT_TYPE_ID
-aspect:xOPERATORvalue	
-Searches for aspect field values. Matches x as a substring of the full path to the aspect type and field name of an aspect that is attached to the entry, in the format projectid.location.ASPECT_TYPE_ID.FIELD_NAME
-
-The list of supported {OPERATOR}s depends on the type of field in the aspect, as follows:
-- String: = (exact match) and : (substring)
-- All number types: =, :, <, >, <=, >=, =>, =<
-- Enum: =
-- Datetime: same as for numbers, but the values to compare are treated as datetimes instead of numbers
-- Boolean: =
-
-Only top-level fields of the aspect are searchable. For example, all of the following queries match entries where the value of the is-enrolled field in the employee-info aspect type is true. Other entries that match on the substring are also returned.
-- aspect:example-project.us-central1.employee-info.is-enrolled=true
-- aspect:example-project.us-central1.employee=true
-- aspect:employee=true
-
-Example:-
-You can use following filters
-- dataplex-types.global.bigquery-table.type={BIGLAKE_TABLE, BIGLAKE_OBJECT_TABLE, EXTERNAL_TABLE, TABLE}
-- dataplex-types.global.storage.type={STRUCTURED, UNSTRUCTURED}
+- "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 are case-sensitive. `OR` and `AND` are acceptable whereas `or` and `and` are not.
+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.
@@ -310,7 +287,7 @@ Logical operators are case-sensitive. `OR` and `AND` are acceptable whereas `or`
 
 ## 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. If you do not know the name of the aspect type, use the `dataplex_search_aspect_types` tool.
+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.
@@ -321,4 +298,4 @@ Logical operators are case-sensitive. `OR` and `AND` are acceptable whereas `or`
 | **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/firebird.md

@@ -1,59 +0,0 @@
----
-title: "Firebird"
-type: docs
-weight: 1
-description: >
-  Firebird is a powerful, cross-platform, and open-source relational database.
-
----
-
-## About
-
-[Firebird][fb-docs] is a relational database management system offering many ANSI SQL standard features that runs on Linux, Windows, and a variety of Unix platforms. It is known for its small footprint, powerful features, and easy maintenance.
-
-[fb-docs]: https://firebirdsql.org/
-
-## Available Tools
-
-- [`firebird-sql`](../tools/firebird/firebird-sql.md)  
-  Execute SQL queries as prepared statements in Firebird.
-
-- [`firebird-execute-sql`](../tools/firebird/firebird-execute-sql.md)  
-  Run parameterized SQL statements in Firebird.
-
-## Requirements
-
-### Database User
-
-This source uses standard authentication. You will need to [create a Firebird user][fb-users] to login to the database with.
-
-[fb-users]: https://firebirdsql.org/refdocs/langrefupd25-sql-create-user.html
-
-## Example
-
-```yaml
-sources:
-    my_firebird_db:
-        kind: firebird
-        host: "localhost"
-        port: 3050
-        database: "/path/to/your/database.fdb"
-        user: ${FIREBIRD_USER}
-        password: ${FIREBIRD_PASS}
-```
-
-{{< 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 "firebird".                                                    |
-| host      |  string  |     true     | IP address to connect to (e.g. "127.0.0.1")                            |
-| port      |  string  |     true     | Port to connect to (e.g. "3050")                                       |
-| database  |  string  |     true     | Path to the Firebird database file (e.g. "/var/lib/firebird/data/test.fdb"). |
-| user      |  string  |     true     | Name of the Firebird user to connect as (e.g. "SYSDBA").               |
-| password  |  string  |     true     | Password of the Firebird user (e.g. "masterkey").                      |

docs/en/resources/sources/looker.md

@@ -39,12 +39,12 @@ sources:
 
 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 number like
+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"
-will be interpreted as false.
+will be interpretted as false.
 
 The client id and client secret are seemingly random character sequences
 assigned by the looker server.

docs/en/resources/sources/mongodb.md

@@ -20,7 +20,9 @@ flexible, JSON-like documents, making it easy to develop and scale applications.
 sources:
     my-mongodb:
         kind: mongodb
-        uri: "mongodb+srv://username:password@host.mongodb.net"       
+        uri: "mongodb+srv://username:password@host.mongodb.net"
+        database: sample_mflix
+        
 ```
 
 ## Reference

docs/en/resources/sources/oceanbase.md

@@ -1,72 +0,0 @@
----
-title: "OceanBase"
-type: docs
-weight: 1
-description: >
-  OceanBase is a distributed relational database that provides high availability, scalability, and compatibility with MySQL.
----
-
-## About
-
-[OceanBase][oceanbase-docs] is a distributed relational database management system (RDBMS) that provides high availability, scalability, and strong consistency. It's designed to handle large-scale data processing and is compatible with MySQL, making it easy for developers to migrate from MySQL to OceanBase.
-
-[oceanbase-docs]: https://www.oceanbase.com/
-
-## Requirements
-
-### Database User
-
-This source only uses standard authentication. You will need to create an OceanBase user to login to the database with. OceanBase supports MySQL-compatible user management syntax.
-
-### Network Connectivity
-
-Ensure that your application can connect to the OceanBase cluster. OceanBase typically runs on ports 2881 (for MySQL protocol) or 3881 (for MySQL protocol with SSL).
-
-## Example
-
-```yaml
-sources:
-    my-oceanbase-source:
-        kind: oceanbase
-        host: 127.0.0.1
-        port: 2881
-        database: my_db
-        user: ${USER_NAME}
-        password: ${PASSWORD}
-        queryTimeout: 30s # Optional: query timeout duration
-```
-
-{{< 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 "oceanbase".                                                                            |
-| host         |  string  |     true     | IP address to connect to (e.g. "127.0.0.1").                                                    |
-| port         |  string  |     true     | Port to connect to (e.g. "2881").                                                               |
-| database     |  string  |     true     | Name of the OceanBase database to connect to (e.g. "my_db").                                    |
-| user         |  string  |     true     | Name of the OceanBase user to connect as (e.g. "my-oceanbase-user").                            |
-| password     |  string  |     true     | Password of the OceanBase user (e.g. "my-password").                                            |
-| queryTimeout |  string  |    false     | Maximum time to wait for query execution (e.g. "30s", "2m"). By default, no timeout is applied. |
-
-## Features
-
-### MySQL Compatibility
-
-OceanBase is highly compatible with MySQL, supporting most MySQL SQL syntax, data types, and functions. This makes it easy to migrate existing MySQL applications to OceanBase.
-
-### High Availability
-
-OceanBase provides automatic failover and data replication across multiple nodes, ensuring high availability and data durability.
-
-### Scalability
-
-OceanBase can scale horizontally by adding more nodes to the cluster, making it suitable for large-scale applications.
-
-### Strong Consistency
-
-OceanBase provides strong consistency guarantees, ensuring that all transactions are ACID compliant. 

docs/en/resources/sources/postgres.md

@@ -57,12 +57,11 @@ instead of hardcoding your secrets into the configuration file.
 
 ## Reference
 
-|  **field**  |      **type**      | **required** | **description**                                                        |
-|-------------|:------------------:|:------------:|------------------------------------------------------------------------|
-| kind        |       string       |     true     | Must be "postgres".                                                    |
-| host        |       string       |     true     | IP address to connect to (e.g. "127.0.0.1")                            |
-| port        |       string       |     true     | Port to connect to (e.g. "5432")                                       |
-| database    |       string       |     true     | Name of the Postgres database to connect to (e.g. "my_db").            |
-| user        |       string       |     true     | Name of the Postgres user to connect as (e.g. "my-pg-user").           |
-| password    |       string       |     true     | Password of the Postgres user (e.g. "my-password").                    |
-| queryParams |  map[string]string |     false    | Raw query to be added to the db connection string.                     |
+| **field** | **type** | **required** | **description**                                                        |
+|-----------|:--------:|:------------:|------------------------------------------------------------------------|
+| kind      |  string  |     true     | Must be "postgres".                                                    |
+| host      |  string  |     true     | IP address to connect to (e.g. "127.0.0.1")                            |
+| port      |  string  |     true     | Port to connect to (e.g. "5432")                                       |
+| database  |  string  |     true     | Name of the Postgres database to connect to (e.g. "my_db").            |
+| user      |  string  |     true     | Name of the Postgres user to connect as (e.g. "my-pg-user").           |
+| password  |  string  |     true     | Password of the Postgres user (e.g. "my-password").                    |

docs/en/resources/sources/redis.md

@@ -4,13 +4,13 @@ linkTitle: "Redis"
 type: docs
 weight: 1
 description: >
-    Redis is a in-memory data structure store.
+    Redis is an open-source, in-memory data structure store.
     
 ---
 
 ## About
 
-Redis is a in-memory data structure store, used as a database,
+Redis is an open-source, in-memory data structure store, used as a database,
 cache, and message broker. It supports data structures such as strings, hashes,
 lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, and
 geospatial indexes with radius queries.

docs/en/resources/sources/sqlite.md

@@ -61,7 +61,7 @@ sources:
 
 | **field** | **type** | **required** | **description**                                                                                                     |
 |-----------|:--------:|:------------:|---------------------------------------------------------------------------------------------------------------------|
-| kind      |  string  |     true     | Must be "sqlite".                                                                                                   |
+| kind      |  string  |     true     | Must be "spanner".                                                                                                  |
 | database  |  string  |     true     | Path to SQLite database file, or ":memory:" for an in-memory database.                                              |
 
 ### Connection Properties

docs/en/resources/sources/trino.md

@@ -1,62 +0,0 @@
----
-title: "Trino"
-type: docs
-weight: 1
-description: >
-  Trino is a distributed SQL query engine for big data analytics.
----
-
-## About
-
-[Trino][trino-docs] is a distributed SQL query engine designed for fast analytic queries against data of any size. It allows you to query data where it lives, including Hive, Cassandra, relational databases or even proprietary data stores.
-
-[trino-docs]: https://trino.io/docs/
-
-## Available Tools
-
-- [`trino-sql`](../tools/trino/trino-sql.md)  
-  Execute parameterized SQL queries against Trino.
-
-- [`trino-execute-sql`](../tools/trino/trino-execute-sql.md)  
-  Execute arbitrary SQL queries against Trino.
-
-## Requirements
-
-### Trino Cluster
-
-You need access to a running Trino cluster with appropriate user permissions for the catalogs and schemas you want to query.
-
-## Example
-
-```yaml
-sources:
-    my-trino-source:
-    kind: trino
-    host: trino.example.com
-    port: "8080"
-    user: ${TRINO_USER}  # Optional for anonymous access
-    password: ${TRINO_PASSWORD}  # Optional
-    catalog: hive
-    schema: default
-```
-
-{{< 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 "trino".                                                       |
-| host        |       string       |     true     | Trino coordinator hostname (e.g. "trino.example.com")                 |
-| port        |       string       |     true     | Trino coordinator port (e.g. "8080", "8443")                          |
-| user        |       string       |     false    | Username for authentication (e.g. "analyst"). Optional for anonymous access. |
-| password    |       string       |     false    | Password for basic authentication                                      |
-| catalog     |       string       |     true     | Default catalog to use for queries (e.g. "hive")                      |
-| schema      |       string       |     true     | Default schema to use for queries (e.g. "default")                    |
-| queryTimeout|       string       |     false    | Query timeout duration (e.g. "30m", "1h")                             |
-| accessToken |       string       |     false    | JWT access token for authentication                                    |
-| kerberosEnabled | boolean        |     false    | Enable Kerberos authentication (default: false)                       |
-| sslEnabled  |       boolean      |     false    | Enable SSL/TLS (default: false)                                       |

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

@@ -15,9 +15,8 @@ It's compatible with the following sources:
 
 - [bigquery](../../sources/bigquery.md)
 
-`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.
+`bigquery-execute-sql` takes one input parameter `sql` and runs the sql
+statement against the `source`.
 
 ## Example
 

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

@@ -1,49 +0,0 @@
----
-title: "bigquery-forecast"
-type: docs
-weight: 1
-description: >
-  A "bigquery-forecast" tool forecasts time series data in BigQuery.
-aliases:
-- /resources/tools/bigquery-forecast
----
-
-## About
-
-A `bigquery-forecast` tool forecasts time series data in BigQuery.
-It's compatible with the following sources:
-
-- [bigquery](../../sources/bigquery.md)
-
-`bigquery-forecast` constructs and executes a `SELECT * FROM AI.FORECAST(...)` query based on the provided parameters:
-
-- **history_data** (string, required): This specifies the source of the historical time series data. It can be either a fully qualified BigQuery table ID (e.g., my-project.my_dataset.my_table) or a SQL query that returns the data.
-- **timestamp_col** (string, required): The name of the column in your history_data that contains the timestamps.
-- **data_col** (string, required): The name of the column in your history_data that contains the numeric values to be forecasted.
-- **id_cols** (array of strings, optional): If you are forecasting multiple time series at once (e.g., sales for different products), this parameter takes an array of column names that uniquely identify each series. It defaults to an empty array if not provided.
-- **horizon** (integer, optional): The number of future time steps you want to predict. It defaults to 10 if not specified.
-
-## Example
-
-```yaml
-tools:
- forecast_tool:
-    kind: bigquery-forecast
-    source: my-bigquery-source
-    description: Use this tool to forecast time series data in BigQuery.
-```
-
-## Sample Prompt
-You can use the following sample prompts to call this tool:
-
-- Can you forecast the history time series data in bigquery table `bqml_tutorial.google_analytic`? Use project_id `myproject`.
-- What are the future `total_visits` in bigquery table `bqml_tutorial.google_analytic`?
-
-
-## Reference
-
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "bigquery-forecast".                                                                  |
-| source      |                   string                   |     true     | Name of the source the forecast tool should execute on.                                                    |
-| description |                   string                   |     true     | Description of the tool that is passed to the LLM.                                               |

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

@@ -15,7 +15,7 @@ It's compatible with the following sources:
 
 - [bigquery](../../sources/bigquery.md)
 
-`bigquery-list-table-ids` takes a required `dataset` parameter to specify the dataset
+`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
 tool defaults to using the project defined in the source configuration.

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

@@ -77,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](..#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -107,7 +107,7 @@ tools:
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | SQL statement to execute on.                                                                                                               |
 | 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. |
+| 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

@@ -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](..#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -96,5 +96,5 @@ tools:
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | SQL statement to execute                                                                                                                   |
 | 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. |
+| 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-search-aspect-types.md

@@ -1,62 +0,0 @@
----
-title: "dataplex-search-aspect-types"
-type: docs
-weight: 1
-description: >
-  A "dataplex-search-aspect-types" tool allows to to find aspect types relevant to the query.
-aliases:
-- /resources/tools/dataplex-search-aspect-types
----
-
-## About
-
-A `dataplex-search-aspect-types` tool allows to fetch the metadata template of aspect types based on search query.
-It's compatible with the following sources:
-
-- [dataplex](../../sources/dataplex.md)
-
-`dataplex-search-aspect-types` accepts following parameters optionally:
-
-- `query` - Narrows down the search of aspect types to value of this parameter. If not provided, it fetches all aspect types available to the user.
-- `pageSize` - Number of returned aspect types in the search page. Defaults to `5`.
-- `orderBy` - Specifies the ordering of results. Supported values are: relevance (default), last_modified_timestamp, last_modified_timestamp asc.
-
-## 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
-[dataplex-docs]: https://cloud.google.com/dataplex
-
-## Example
-
-```yaml
-tools:
-  dataplex-search-aspect-types:
-    kind: dataplex-search-aspect-types
-    source: my-dataplex-source
-    description: Use this tool to find aspect types relevant to the query.
-```
-
-## Reference
-
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "dataplex-search-aspect-types".                                                          |
-| 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

@@ -17,11 +17,22 @@ It's compatible with the following sources:
 - [dataplex](../../sources/dataplex.md)
 
 `dataplex-search-entries` takes a required `query` parameter based on which
-entries are filtered and returned to the user. It also optionally accepts following parameters:
+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.
+  (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
 

docs/en/resources/tools/firebird/_index.md

@@ -1,7 +0,0 @@
----
-title: "Firebird"
-type: docs
-weight: 1
-description: > 
-  Tools that work with Firebird Sources.
----

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

@@ -1,41 +0,0 @@
----
-title: "firebird-execute-sql"
-type: docs
-weight: 1
-description: > 
-  A "firebird-execute-sql" tool executes a SQL statement against a Firebird
-  database.
-aliases:
-- /resources/tools/firebird-execute-sql
----
-
-## About
-
-A `firebird-execute-sql` tool executes a SQL statement against a Firebird
-database. It's compatible with the following source:
-
-- [firebird](../sources/firebird.md)
-
-`firebird-execute-sql` takes one input parameter `sql` and runs the sql
-statement 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.
-
-## Example
-
-```yaml
-tools:
-  execute_sql_tool:
-    kind: firebird-execute-sql
-    source: my_firebird_db
-    description: Use this tool to execute a SQL statement against the Firebird database.
-```
-
-## Reference
-
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "firebird-execute-sql".                                                                  |
-| 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/firebird/firebird-sql.md

@@ -1,135 +0,0 @@
----
-title: "firebird-sql"
-type: docs
-weight: 1
-description: > 
-  A "firebird-sql" tool executes a pre-defined SQL statement against a Firebird
-  database.
-aliases:
-- /resources/tools/firebird-sql
----
-
-## About
-
-A `firebird-sql` tool executes a pre-defined SQL statement against a Firebird
-database. It's compatible with the following source:
-
-- [firebird](../sources/firebird.md)
-
-The specified SQL statement is executed as a [prepared statement][fb-prepare],
-and supports both positional parameters (`?`) and named parameters (`:param_name`).
-Parameters will be inserted according to their position or name. If template 
-parameters are included, they will be resolved before the execution of the 
-prepared statement.
-
-[fb-prepare]: https://firebirdsql.org/refdocs/langrefupd25-psql-execstat.html
-
-## Example
-
-> **Note:** This tool uses parameterized queries to prevent SQL injections.
-> Query parameters can be used as substitutes for arbitrary expressions.
-> Parameters cannot be used as substitutes for identifiers, column names, table
-> names, or other parts of the query.
-
-```yaml
-tools:
-  search_flights_by_number:
-    kind: firebird-sql
-    source: my_firebird_db
-    statement: |
-      SELECT * FROM flights
-      WHERE airline = ?
-      AND flight_number = ?
-      LIMIT 10
-    description: |
-      Use this tool to get information for a specific flight.
-      Takes an airline code and flight number and returns info on the flight.
-      Do NOT use this tool with a flight id. Do NOT guess an airline code or flight number.
-      A airline code is a code for an airline service consisting of two-character
-      airline designator and followed by flight number, which is 1 to 4 digit number.
-      For example, if given CY 0123, the airline is "CY", and flight_number is "123".
-      Another example for this is DL 1234, the airline is "DL", and flight_number is "1234".
-      If the tool returns more than one option choose the date closes to today.
-      Example:
-      {{
-          "airline": "CY",
-          "flight_number": "888",
-      }}
-      Example:
-      {{
-          "airline": "DL",
-          "flight_number": "1234",
-      }}
-    parameters:
-      - name: airline
-        type: string
-        description: Airline unique 2 letter identifier
-      - name: flight_number
-        type: string
-        description: 1 to 4 digit number
-```
-
-### Example with Named Parameters
-
-```yaml
-tools:
-  search_flights_by_airline:
-    kind: firebird-sql
-    source: my_firebird_db
-    statement: |
-      SELECT * FROM flights
-      WHERE airline = :airline
-      AND departure_date >= :start_date
-      AND departure_date <= :end_date
-      ORDER BY departure_date
-    description: |
-      Search for flights by airline within a date range using named parameters.
-    parameters:
-      - name: airline
-        type: string
-        description: Airline unique 2 letter identifier
-      - name: start_date
-        type: string
-        description: Start date in YYYY-MM-DD format
-      - name: end_date
-        type: string
-        description: End date in YYYY-MM-DD format
-```
-
-### Example with Template Parameters
-
-> **Note:** This tool allows direct modifications to the SQL statement,
-> 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).
-
-```yaml
-tools:
-  list_table:
-    kind: firebird-sql
-    source: my_firebird_db
-    statement: |
-      SELECT * FROM {{.tableName}}
-    description: |
-      Use this tool to list all information from a specific table.
-      Example:
-      {{
-          "tableName": "flights",
-      }}
-    templateParameters:
-      - name: tableName
-        type: string
-        description: Table to select from
-```
-
-## Reference
-
-| **field**           |                  **type**                                 | **required** | **description**                                                                                                                            |
-|---------------------|:---------------------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------------------------------------------------|
-| kind                |                   string                                  |     true     | Must be "firebird-sql".                                                                                                                    |
-| 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. |

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

@@ -1,274 +0,0 @@
----
-title: "firestore-add-documents"
-type: docs
-weight: 1
-description: >
-  A "firestore-add-documents" tool adds document to a given collection path.
-aliases:
-- /resources/tools/firestore-add-documents
----
-## Description
-
-The `firestore-add-documents` tool allows you to add new documents to a Firestore collection. It supports all Firestore data types using Firestore's native JSON format. The tool automatically generates a unique document ID for each new document.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `collectionPath` | string | Yes | The path of the collection where the document will be added |
-| `documentData` | map | Yes | The data to be added as a document to the given collection. Must use [Firestore's native JSON format](https://cloud.google.com/firestore/docs/reference/rest/Shared.Types/ArrayValue#Value) with typed values |
-| `returnData` | boolean | No | If set to true, the output will include the data of the created document. Defaults to false to help avoid overloading the context |
-
-## Output
-
-The tool returns a map containing:
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `documentPath` | string | The full resource name of the created document (e.g., `projects/{projectId}/databases/{databaseId}/documents/{document_path}`) |
-| `createTime` | string | The timestamp when the document was created |
-| `documentData` | map | The data that was added (only included when `returnData` is true) |
-
-## Data Type Format
-
-The tool requires Firestore's native JSON format for document data. Each field must be wrapped with its type indicator:
-
-### Basic Types
-- **String**: `{"stringValue": "your string"}`
-- **Integer**: `{"integerValue": "123"}` or `{"integerValue": 123}`
-- **Double**: `{"doubleValue": 123.45}`
-- **Boolean**: `{"booleanValue": true}`
-- **Null**: `{"nullValue": null}`
-- **Bytes**: `{"bytesValue": "base64EncodedString"}`
-- **Timestamp**: `{"timestampValue": "2025-01-07T10:00:00Z"}` (RFC3339 format)
-
-### Complex Types
-- **GeoPoint**: `{"geoPointValue": {"latitude": 34.052235, "longitude": -118.243683}}`
-- **Array**: `{"arrayValue": {"values": [{"stringValue": "item1"}, {"integerValue": "2"}]}}`
-- **Map**: `{"mapValue": {"fields": {"key1": {"stringValue": "value1"}, "key2": {"booleanValue": true}}}}`
-- **Reference**: `{"referenceValue": "collection/document"}`
-
-## Examples
-
-### Basic Document Creation
-
-```yaml
-tools:
-  add-company-doc:
-    kind: firestore-add-documents
-    source: my-firestore
-    description: Add a new company document
-```
-
-Usage:
-```json
-{
-  "collectionPath": "companies",
-  "documentData": {
-    "name": {
-      "stringValue": "Acme Corporation"
-    },
-    "establishmentDate": {
-      "timestampValue": "2000-01-15T10:30:00Z"
-    },
-    "location": {
-      "geoPointValue": {
-        "latitude": 34.052235,
-        "longitude": -118.243683
-      }
-    },
-    "active": {
-      "booleanValue": true
-    },
-    "employeeCount": {
-      "integerValue": "1500"
-    },
-    "annualRevenue": {
-      "doubleValue": 1234567.89
-    }
-  }
-}
-```
-
-### With Nested Maps and Arrays
-
-```json
-{
-  "collectionPath": "companies",
-  "documentData": {
-    "name": {
-      "stringValue": "Tech Innovations Inc"
-    },
-    "contactInfo": {
-      "mapValue": {
-        "fields": {
-          "email": {
-            "stringValue": "info@techinnovations.com"
-          },
-          "phone": {
-            "stringValue": "+1-555-123-4567"
-          },
-          "address": {
-            "mapValue": {
-              "fields": {
-                "street": {
-                  "stringValue": "123 Innovation Drive"
-                },
-                "city": {
-                  "stringValue": "San Francisco"
-                },
-                "state": {
-                  "stringValue": "CA"
-                },
-                "zipCode": {
-                  "stringValue": "94105"
-                }
-              }
-            }
-          }
-        }
-      }
-    },
-    "products": {
-      "arrayValue": {
-        "values": [
-          {
-            "stringValue": "Product A"
-          },
-          {
-            "stringValue": "Product B"
-          },
-          {
-            "mapValue": {
-              "fields": {
-                "productName": {
-                  "stringValue": "Product C Premium"
-                },
-                "version": {
-                  "integerValue": "3"
-                },
-                "features": {
-                  "arrayValue": {
-                    "values": [
-                      {
-                        "stringValue": "Advanced Analytics"
-                      },
-                      {
-                        "stringValue": "Real-time Sync"
-                      }
-                    ]
-                  }
-                }
-              }
-            }
-          }
-        ]
-      }
-    }
-  },
-  "returnData": true
-}
-```
-
-### Complete Example with All Data Types
-
-```json
-{
-  "collectionPath": "test-documents",
-  "documentData": {
-    "stringField": {
-      "stringValue": "Hello World"
-    },
-    "integerField": {
-      "integerValue": "42"
-    },
-    "doubleField": {
-      "doubleValue": 3.14159
-    },
-    "booleanField": {
-      "booleanValue": true
-    },
-    "nullField": {
-      "nullValue": null
-    },
-    "timestampField": {
-      "timestampValue": "2025-01-07T15:30:00Z"
-    },
-    "geoPointField": {
-      "geoPointValue": {
-        "latitude": 37.7749,
-        "longitude": -122.4194
-      }
-    },
-    "bytesField": {
-      "bytesValue": "SGVsbG8gV29ybGQh"
-    },
-    "arrayField": {
-      "arrayValue": {
-        "values": [
-          {
-            "stringValue": "item1"
-          },
-          {
-            "integerValue": "2"
-          },
-          {
-            "booleanValue": false
-          }
-        ]
-      }
-    },
-    "mapField": {
-      "mapValue": {
-        "fields": {
-          "nestedString": {
-            "stringValue": "nested value"
-          },
-          "nestedNumber": {
-            "doubleValue": 99.99
-          }
-        }
-      }
-    }
-  }
-}
-```
-
-## Authentication
-
-The tool can be configured to require authentication:
-
-```yaml
-tools:
-  secure-add-docs:
-    kind: firestore-add-documents
-    source: prod-firestore
-    description: Add documents with authentication required
-    authRequired:
-      - google-oauth
-      - api-key
-```
-
-## Error Handling
-
-Common errors include:
-- Invalid collection path
-- Missing or invalid document data
-- Permission denied (if Firestore security rules block the operation)
-- Invalid data type conversions
-
-## Best Practices
-
-1. **Always use typed values**: Every field must be wrapped with its appropriate type indicator (e.g., `{"stringValue": "text"}`)
-2. **Integer values can be strings**: The tool accepts integer values as strings (e.g., `{"integerValue": "1500"}`)
-3. **Use returnData sparingly**: Only set to true when you need to verify the exact data that was written
-4. **Validate data before sending**: Ensure your data matches Firestore's native JSON format
-5. **Handle timestamps properly**: Use RFC3339 format for timestamp strings
-6. **Base64 encode binary data**: Binary data must be base64 encoded in the `bytesValue` field
-7. **Consider security rules**: Ensure your Firestore security rules allow document creation in the target collection
-
-## Related Tools
-
-- [`firestore-get-documents`](firestore-get-documents.md) - Retrieve documents by their paths
-- [`firestore-query-collection`](firestore-query-collection.md) - Query documents in a collection
-- [`firestore-delete-documents`](firestore-delete-documents.md) - Delete documents from Firestore

docs/en/resources/tools/firestore/firestore-update-document.md

@@ -1,327 +0,0 @@
----
-title: "firestore-update-document"
-type: docs
-weight: 1
-description: >
-  A "firestore-update-document" tool updates an existing document in Firestore.
-aliases:
-- /resources/tools/firestore-update-document
----
-## Description
-
-The `firestore-update-document` tool allows you to update existing documents in Firestore. It supports all Firestore data types using Firestore's native JSON format. The tool can perform both full document updates (replacing all fields) or selective field updates using an update mask. When using an update mask, fields referenced in the mask but not present in the document data will be deleted from the document, following Firestore's native behavior.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `documentPath` | string | Yes | The path of the document which needs to be updated |
-| `documentData` | map | Yes | The data to update in the document. Must use [Firestore's native JSON format](https://cloud.google.com/firestore/docs/reference/rest/Shared.Types/ArrayValue#Value) with typed values |
-| `updateMask` | array | No | The selective fields to update. If not provided, all fields in documentData will be updated. When provided, only the specified fields will be updated. Fields referenced in the mask but not present in documentData will be deleted from the document |
-| `returnData` | boolean | No | If set to true, the output will include the data of the updated document. Defaults to false to help avoid overloading the context |
-
-## Output
-
-The tool returns a map containing:
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `documentPath` | string | The full path of the updated document |
-| `updateTime` | string | The timestamp when the document was updated |
-| `documentData` | map | The current data of the document after the update (only included when `returnData` is true) |
-
-## Data Type Format
-
-The tool requires Firestore's native JSON format for document data. Each field must be wrapped with its type indicator:
-
-### Basic Types
-- **String**: `{"stringValue": "your string"}`
-- **Integer**: `{"integerValue": "123"}` or `{"integerValue": 123}`
-- **Double**: `{"doubleValue": 123.45}`
-- **Boolean**: `{"booleanValue": true}`
-- **Null**: `{"nullValue": null}`
-- **Bytes**: `{"bytesValue": "base64EncodedString"}`
-- **Timestamp**: `{"timestampValue": "2025-01-07T10:00:00Z"}` (RFC3339 format)
-
-### Complex Types
-- **GeoPoint**: `{"geoPointValue": {"latitude": 34.052235, "longitude": -118.243683}}`
-- **Array**: `{"arrayValue": {"values": [{"stringValue": "item1"}, {"integerValue": "2"}]}}`
-- **Map**: `{"mapValue": {"fields": {"key1": {"stringValue": "value1"}, "key2": {"booleanValue": true}}}}`
-- **Reference**: `{"referenceValue": "collection/document"}`
-
-## Update Modes
-
-### Full Document Update (Merge All)
-
-When `updateMask` is not provided, the tool performs a merge operation that updates all fields specified in `documentData` while preserving other existing fields in the document.
-
-### Selective Field Update
-
-When `updateMask` is provided, only the fields listed in the mask are updated. This allows for precise control over which fields are modified, added, or deleted. To delete a field, include it in the `updateMask` but omit it from `documentData`.
-
-## Reference
-
-| **field**   |     **type**   | **required** | **description**                                          |
-|-------------|:--------------:|:------------:|----------------------------------------------------------|
-| kind        |     string     |     true     | Must be "firestore-update-document".                     |
-| source      |     string     |     true     | Name of the Firestore source to update documents in.     |
-| description |     string     |     true     | Description of the tool that is passed to the LLM.       |
-
-
-## Examples
-
-### Basic Document Update (Full Merge)
-
-```yaml
-tools:
-  update-user-doc:
-    kind: firestore-update-document
-    source: my-firestore
-    description: Update a user document
-```
-Usage:
-```json
-{
-  "documentPath": "users/user123",
-  "documentData": {
-    "name": {
-      "stringValue": "Jane Doe"
-    },
-    "lastUpdated": {
-      "timestampValue": "2025-01-15T10:30:00Z"
-    },
-    "status": {
-      "stringValue": "active"
-    },
-    "score": {
-      "integerValue": "150"
-    }
-  }
-}
-```
-
-### Selective Field Update with Update Mask
-
-```json
-{
-  "documentPath": "users/user123",
-  "documentData": {
-    "email": {
-      "stringValue": "newemail@example.com"
-    },
-    "profile": {
-      "mapValue": {
-        "fields": {
-          "bio": {
-            "stringValue": "Updated bio text"
-          },
-          "avatar": {
-            "stringValue": "https://example.com/new-avatar.jpg"
-          }
-        }
-      }
-    }
-  },
-  "updateMask": ["email", "profile.bio", "profile.avatar"]
-}
-```
-
-### Update with Field Deletion
-
-To delete fields, include them in the `updateMask` but omit them from `documentData`:
-
-```json
-{
-  "documentPath": "users/user123",
-  "documentData": {
-    "name": {
-      "stringValue": "John Smith"
-    }
-  },
-  "updateMask": ["name", "temporaryField", "obsoleteData"],
-  "returnData": true
-}
-```
-
-In this example:
-- `name` will be updated to "John Smith"
-- `temporaryField` and `obsoleteData` will be deleted from the document (they are in the mask but not in the data)
-
-### Complex Update with Nested Data
-
-```json
-{
-  "documentPath": "companies/company456",
-  "documentData": {
-    "metadata": {
-      "mapValue": {
-        "fields": {
-          "lastModified": {
-            "timestampValue": "2025-01-15T14:30:00Z"
-          },
-          "modifiedBy": {
-            "stringValue": "admin@company.com"
-          }
-        }
-      }
-    },
-    "locations": {
-      "arrayValue": {
-        "values": [
-          {
-            "mapValue": {
-              "fields": {
-                "city": {
-                  "stringValue": "San Francisco"
-                },
-                "coordinates": {
-                  "geoPointValue": {
-                    "latitude": 37.7749,
-                    "longitude": -122.4194
-                  }
-                }
-              }
-            }
-          },
-          {
-            "mapValue": {
-              "fields": {
-                "city": {
-                  "stringValue": "New York"
-                },
-                "coordinates": {
-                  "geoPointValue": {
-                    "latitude": 40.7128,
-                    "longitude": -74.0060
-                  }
-                }
-              }
-            }
-          }
-        ]
-      }
-    },
-    "revenue": {
-      "doubleValue": 5678901.23
-    }
-  },
-  "updateMask": ["metadata", "locations", "revenue"]
-}
-```
-
-### Update with All Data Types
-
-```json
-{
-  "documentPath": "test-documents/doc789",
-  "documentData": {
-    "stringField": {
-      "stringValue": "Updated string"
-    },
-    "integerField": {
-      "integerValue": "999"
-    },
-    "doubleField": {
-      "doubleValue": 2.71828
-    },
-    "booleanField": {
-      "booleanValue": false
-    },
-    "nullField": {
-      "nullValue": null
-    },
-    "timestampField": {
-      "timestampValue": "2025-01-15T16:45:00Z"
-    },
-    "geoPointField": {
-      "geoPointValue": {
-        "latitude": 51.5074,
-        "longitude": -0.1278
-      }
-    },
-    "bytesField": {
-      "bytesValue": "VXBkYXRlZCBkYXRh"
-    },
-    "arrayField": {
-      "arrayValue": {
-        "values": [
-          {
-            "stringValue": "updated1"
-          },
-          {
-            "integerValue": "200"
-          },
-          {
-            "booleanValue": true
-          }
-        ]
-      }
-    },
-    "mapField": {
-      "mapValue": {
-        "fields": {
-          "nestedString": {
-            "stringValue": "updated nested value"
-          },
-          "nestedNumber": {
-            "doubleValue": 88.88
-          }
-        }
-      }
-    },
-    "referenceField": {
-      "referenceValue": "users/updatedUser"
-    }
-  },
-  "returnData": true
-}
-```
-
-## Authentication
-
-The tool can be configured to require authentication:
-
-```yaml
-tools:
-  secure-update-doc:
-    kind: firestore-update-document
-    source: prod-firestore
-    description: Update documents with authentication required
-    authRequired:
-      - google-oauth
-      - api-key
-```
-## Error Handling
-Common errors include:
-- Document not found (when using update with a non-existent document)
-- Invalid document path
-- Missing or invalid document data
-- Permission denied (if Firestore security rules block the operation)
-- Invalid data type conversions
-
-## Best Practices
-1. **Use update masks for precision**: When you only need to update specific fields, use the `updateMask` parameter to avoid unintended changes
-2. **Always use typed values**: Every field must be wrapped with its appropriate type indicator (e.g., `{"stringValue": "text"}`)
-3. **Integer values can be strings**: The tool accepts integer values as strings (e.g., `{"integerValue": "1500"}`)
-4. **Use returnData sparingly**: Only set to true when you need to verify the exact data after the update
-5. **Validate data before sending**: Ensure your data matches Firestore's native JSON format
-6. **Handle timestamps properly**: Use RFC3339 format for timestamp strings
-7. **Base64 encode binary data**: Binary data must be base64 encoded in the `bytesValue` field
-8. **Consider security rules**: Ensure your Firestore security rules allow document updates
-9. **Delete fields using update mask**: To delete fields, include them in the `updateMask` but omit them from `documentData`
-10. **Test with non-production data first**: Always test your updates on non-critical documents first
-
-## Differences from Add Documents
-
-- **Purpose**: Updates existing documents vs. creating new ones
-- **Document must exist**: For standard updates (though not using updateMask will create if missing with given document id)
-- **Update mask support**: Allows selective field updates
-- **Field deletion**: Supports removing specific fields by including them in the mask but not in the data
-- **Returns updateTime**: Instead of createTime
-
-## Related Tools
-
-- [`firestore-add-documents`](firestore-add-documents.md) - Add new documents to Firestore
-- [`firestore-get-documents`](firestore-get-documents.md) - Retrieve documents by their paths
-- [`firestore-query-collection`](firestore-query-collection.md) - Query documents in a collection
-- [`firestore-delete-documents`](firestore-delete-documents.md) - Delete documents from Firestore

docs/en/resources/tools/looker/looker-add-dashboard-element.md

@@ -1,63 +0,0 @@
----
-title: "looker-add-dashboard-element"
-type: docs
-weight: 1
-description: >
-  "looker-add-dashboard-element" generates a Looker look in the users personal folder in
-  Looker
-aliases:
-- /resources/tools/looker-add-dashboard-element
----
-
-## About
-
-The `looker-add-dashboard-element` creates a dashboard element
-in the given dashboard.
-
-It's compatible with the following sources:
-
-- [looker](../../sources/looker.md)
-
-`looker-add-dashboard-element` takes eleven 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. the `dashboard_id`
-
-## Example
-
-```yaml
-tools:
-    add_dashboard_element:
-        kind: looker-add-dashboard-element
-        source: looker-source
-        description: |
-          add_dashboard_element Tool
-
-          This tool creates a new tile in a Looker dashboard 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 that may be provided.
-          The dashboard_id must be specified. That is obtained
-          from calling make_dashboard.
-
-          This tool can be called many times for one dashboard_id
-          and the resulting tiles will be added in order.
-```
-
-## Reference
-
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "looker-add-dashboard-element"                                                           |
-| 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-get-dashboards.md

@@ -1,60 +0,0 @@
----
-title: "looker-get-dashboards"
-type: docs
-weight: 1
-description: >
-  "looker-get-dashboards" searches for saved Looks in a Looker
-  source.
-aliases:
-- /resources/tools/looker-get-dashboards
----
-
-## About
-
-The `looker-get-dashboards` tool searches for a saved Dashboard by
-name or description.
-
-It's compatible with the following sources:
-
-- [looker](../../sources/looker.md)
-
-`looker-get-dashboards` takes four parameters, the `title`, `desc`, `limit`
-and `offset`.
-
-Title and description use SQL style wildcards and are case insensitive.
-
-Limit and offset are used to page through a larger set of matches and
-default to 100 and 0.
-
-## Example
-
-```yaml
-tools:
-    get_dashboards:
-        kind: looker-get-dashboards
-        source: looker-source
-        description: |
-          get_dashboards Tool
-
-          This tool is used to search for saved dashboards in a Looker instance.
-          String search params use case-insensitive matching. String search
-          params can contain % and '_' as SQL LIKE pattern match wildcard
-          expressions. example="dan%" will match "danger" and "Danzig" but
-          not "David" example="D_m%" will match "Damage" and "dump".
-
-          Most search params can accept "IS NULL" and "NOT NULL" as special
-          expressions to match or exclude (respectively) rows where the
-          column is null.
-
-          The limit and offset are used to paginate the results.
-
-          The result of the get_dashboards tool is a list of json objects.
-```
-
-## Reference
-
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "looker-get-dashboards"                                                                  |
-| 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-make-dashboard.md

@@ -1,53 +0,0 @@
----
-title: "looker-make-dashboard"
-type: docs
-weight: 1
-description: >
-  "looker-make-dashboard" generates a Looker dashboard in the users personal folder in
-  Looker
-aliases:
-- /resources/tools/looker-make-dashboard
----
-
-## About
-
-The `looker-make-dashboard` creates a dashboard in the user's
-Looker personal folder.
-
-It's compatible with the following sources:
-
-- [looker](../../sources/looker.md)
-
-`looker-make-dashboard` takes one parameter:
-
-1. the `title`
-
-## Example
-
-```yaml
-tools:
-    make_dashboard:
-        kind: looker-make-dashboard
-        source: looker-source
-        description: |
-          make_dashboard Tool
-
-          This tool creates a new dashboard in Looker. The dashboard is
-          initially empty and the add_dashboard_element tool is used to
-          add content to the dashboard.
-
-          The newly created dashboard will be created in the user's
-          personal folder in looker. The dashboard name must be unique.
-
-          The result is a json document with a link to the newly
-          created dashboard and the id of the dashboard. Use the id
-          when calling add_dashboard_element.
-```
-
-## Reference
-
-| **field**   |                  **type**                  | **required** | **description**                                                                                  |
-|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "looker-make-dashboard"                                                                  |
-| 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-url.md

@@ -1,492 +0,0 @@
----
-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 nine 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. Here are
-          some notes on making visualizations.
-
-          ### Cartesian Charts (Area, Bar, Column, Line, Scatter)
-
-          These chart types share a large number of configuration options.
-
-          **General**
-          *   `type`: The type of visualization (`looker_area`, `looker_bar`, `looker_column`, `looker_line`, `looker_scatter`).
-          *   `series_types`: Override the chart type for individual series.
-          *   `show_view_names`: Display view names in labels and tooltips (`true`/`false`).
-          *   `series_labels`: Provide custom names for series.
-
-          **Styling & Colors**
-          *   `colors`: An array of color values to be used for the chart series.
-          *   `series_colors`: A mapping of series names to specific color values.
-          *   `color_application`: Advanced controls for color palette application (collection, palette, reverse, etc.).
-          *   `font_size`: Font size for labels (e.g., '12px').
-
-          **Legend**
-          *   `hide_legend`: Show or hide the chart legend (`true`/`false`).
-          *   `legend_position`: Placement of the legend (`'center'`, `'left'`, `'right'`).
-
-          **Axes**
-          *   `swap_axes`: Swap the X and Y axes (`true`/`false`).
-          *   `x_axis_scale`: Scale of the x-axis (`'auto'`, `'ordinal'`, `'linear'`, `'time'`).
-          *   `x_axis_reversed`, `y_axis_reversed`: Reverse the direction of an axis (`true`/`false`).
-          *   `x_axis_gridlines`, `y_axis_gridlines`: Display gridlines for an axis (`true`/`false`).
-          *   `show_x_axis_label`, `show_y_axis_label`: Show or hide the axis title (`true`/`false`).
-          *   `show_x_axis_ticks`, `show_y_axis_ticks`: Show or hide axis tick marks (`true`/`false`).
-          *   `x_axis_label`, `y_axis_label`: Set a custom title for an axis.
-          *   `x_axis_datetime_label`: A format string for datetime labels on the x-axis (e.g., `'%Y-%m'`).
-          *   `x_padding_left`, `x_padding_right`: Adjust padding on the ends of the x-axis.
-          *   `x_axis_label_rotation`, `x_axis_label_rotation_bar`: Set rotation for x-axis labels.
-          *   `x_axis_zoom`, `y_axis_zoom`: Enable zooming on an axis (`true`/`false`).
-          *   `y_axes`: An array of configuration objects for multiple y-axes.
-
-          **Data & Series**
-          *   `stacking`: How to stack series (`''` for none, `'normal'`, `'percent'`).
-          *   `ordering`: Order of series in a stack (`'none'`, etc.).
-          *   `limit_displayed_rows`: Enable or disable limiting the number of rows displayed (`true`/`false`).
-          *   `limit_displayed_rows_values`: Configuration for the row limit (e.g., `{ "first_last": "first", "show_hide": "show", "num_rows": 10 }`).
-          *   `discontinuous_nulls`: How to render null values in line charts (`true`/`false`).
-          *   `point_style`: Style for points on line and area charts (`'none'`, `'circle'`, `'circle_outline'`).
-          *   `series_point_styles`: Override point styles for individual series.
-          *   `interpolation`: Line interpolation style (`'linear'`, `'monotone'`, `'step'`, etc.).
-          *   `show_value_labels`: Display values on data points (`true`/`false`).
-          *   `label_value_format`: A format string for value labels.
-          *   `show_totals_labels`: Display total labels on stacked charts (`true`/`false`).
-          *   `totals_color`: Color for total labels.
-          *   `show_silhouette`: Display a "silhouette" of hidden series in stacked charts (`true`/`false`).
-          *   `hidden_series`: An array of series names to hide from the visualization.
-
-          **Scatter/Bubble Specific**
-          *   `size_by_field`: The field used to determine the size of bubbles.
-          *   `color_by_field`: The field used to determine the color of bubbles.
-          *   `plot_size_by_field`: Whether to display the size-by field in the legend.
-          *   `cluster_points`: Group nearby points into clusters (`true`/`false`).
-          *   `quadrants_enabled`: Display quadrants on the chart (`true`/`false`).
-          *   `quadrant_properties`: Configuration for quadrant labels and colors.
-          *   `custom_quadrant_value_x`, `custom_quadrant_value_y`: Set quadrant boundaries as a percentage.
-          *   `custom_quadrant_point_x`, `custom_quadrant_point_y`: Set quadrant boundaries to a specific value.
-
-          **Miscellaneous**
-          *   `reference_lines`: Configuration for displaying reference lines.
-          *   `trend_lines`: Configuration for displaying trend lines.
-          *   `trellis`: Configuration for creating trellis (small multiple) charts.
-          *   `crossfilterEnabled`, `crossfilters`: Configuration for cross-filtering interactions.
-
-          ### Boxplot
-
-          *   Inherits most of the Cartesian chart options.
-          *   `type`: Must be `looker_boxplot`.
-
-          ### Funnel
-
-          *   `type`: Must be `looker_funnel`.
-          *   `orientation`: How data is read (`'automatic'`, `'dataInRows'`, `'dataInColumns'`).
-          *   `percentType`: How percentages are calculated (`'percentOfMaxValue'`, `'percentOfPriorRow'`).
-          *   `labelPosition`, `valuePosition`, `percentPosition`: Placement of labels (`'left'`, `'right'`, `'inline'`, `'hidden'`).
-          *   `labelColor`, `labelColorEnabled`: Set a custom color for labels.
-          *   `labelOverlap`: Allow labels to overlap (`true`/`false`).
-          *   `barColors`: An array of colors for the funnel steps.
-          *   `color_application`: Advanced color palette controls.
-          *   `crossfilterEnabled`, `crossfilters`: Configuration for cross-filtering.
-
-          ### Pie / Donut
-
-          *   `type`: Must be `looker_pie`.
-          *   `value_labels`: Where to display values (`'legend'`, `'labels'`).
-          *   `label_type`: The format of data labels (`'labPer'`, `'labVal'`, `'lab'`, `'val'`, `'per'`).
-          *   `start_angle`, `end_angle`: The start and end angles of the pie chart.
-          *   `inner_radius`: The inner radius, used to create a donut chart.
-          *   `series_colors`, `series_labels`: Override colors and labels for specific slices.
-          *   `color_application`: Advanced color palette controls.
-          *   `crossfilterEnabled`, `crossfilters`: Configuration for cross-filtering.
-          *   `advanced_vis_config`: A string containing JSON for advanced Highcharts configuration.
-
-          ### Waterfall
-
-          *   Inherits most of the Cartesian chart options.
-          *   `type`: Must be `looker_waterfall`.
-          *   `up_color`: Color for positive (increasing) values.
-          *   `down_color`: Color for negative (decreasing) values.
-          *   `total_color`: Color for the total bar.
-
-          ### Word Cloud
-
-          *   `type`: Must be `looker_wordcloud`.
-          *   `rotation`: Enable random word rotation (`true`/`false`).
-          *   `colors`: An array of colors for the words.
-          *   `color_application`: Advanced color palette controls.
-          *   `crossfilterEnabled`, `crossfilters`: Configuration for cross-filtering.
-
-          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 record visualization -
-          {{
-            "defaults_version": 1,
-            "show_view_names": false,
-            "type": "looker_single_record"
-          }}
-
-          A single value visualization -
-          {{
-            "comparison_reverse_colors": false,
-            "comparison_type": "value",                                                                                                                                            "conditional_formatting_include_nulls": false,                                                                                                                         "conditional_formatting_include_totals": false,
-            "custom_color": "#1A73E8",
-            "custom_color_enabled": true,
-            "defaults_version": 1,
-            "enable_conditional_formatting": false,
-            "series_types": {},
-            "show_comparison": false,
-            "show_comparison_label": true,
-            "show_single_value_title": true,
-            "single_value_title": "Total Clicks",
-            "type": "single_value"
-          }}
-
-          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_get_dimensions.md

@@ -12,7 +12,7 @@ aliases:
 ## About
 
 A `looker-get-dimensions` tool returns all the dimensions from a given explore
-in a given model in the source.
+in a given mode in the source.
 
 It's compatible with the following sources:
 

docs/en/resources/tools/looker/looker_get_filters.md

@@ -12,7 +12,7 @@ aliases:
 ## About
 
 A `looker-get-filters` tool returns all the filters from a given explore
-in a given model in the source.
+in a given mode in the source.
 
 It's compatible with the following sources:
 

docs/en/resources/tools/looker/looker_get_measures.md

@@ -12,7 +12,7 @@ aliases:
 ## About
 
 A `looker-get-measures` tool returns all the measures from a given explore
-in a given model in the source.
+in a given mode in the source.
 
 It's compatible with the following sources:
 

docs/en/resources/tools/looker/looker_get_models.md

@@ -10,7 +10,7 @@ aliases:
 
 ## About
 
-A `looker-get-models` tool returns all the models in the source.
+A `looker-get-models` tool returns all the models the source.
 
 It's compatible with the following sources:
 

docs/en/resources/tools/looker/looker_get_parameters.md

@@ -12,7 +12,7 @@ aliases:
 ## About
 
 A `looker-get-parameters` tool returns all the parameters from a given explore
-in a given model in the source.
+in a given mode in the source.
 
 It's compatible with the following sources:
 

docs/en/resources/tools/looker/looker_query_url.md

@@ -1,24 +1,23 @@
 ---
-title: "looker-make-look"
+title: "looker-query-url"
 type: docs
 weight: 1
 description: >
-  "looker-make-look" generates a Looker look in the users personal folder in
-  Looker
+  "looker-query-url" generates a url link to a Looker explore.
 aliases:
-- /resources/tools/looker-make-look
+- /resources/tools/looker-query-url
 ---
 
 ## About
 
-The `looker-make-look` creates a saved Look in the user's
-Looker personal folder.
+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-make-look` takes eleven parameters:
+`looker-query-url` takes eight parameters:
 
 1. the `model`
 2. the `explore`
@@ -28,38 +27,27 @@ It's compatible with the following sources:
 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
+    query_url:
+        kind: looker-query-url
         source: looker-source
         description: |
-          make_look Tool
+          Query URL 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.
+          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 `looker-query` tool.
 ```
 
 ## Reference
 
 | **field**   |                  **type**                  | **required** | **description**                                                                                  |
 |-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        |                   string                   |     true     | Must be "looker-make-look"                                                                       |
+| 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/mssql/mssql-sql.md

@@ -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](..#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -108,4 +108,4 @@ tools:
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | SQL statement to execute.                                                                                                                  |
 | 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. |
+| 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-sql.md

@@ -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](..#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -103,4 +103,4 @@ tools:
 | description        |                   string                         |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement          |                   string                         |     true     | SQL statement to execute on.                                                                                                               |
 | 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. |
+| 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

@@ -42,7 +42,7 @@ tools:
       LIMIT 10
     description: |
       Use this tool to get a list of movies for a specific actor and a given minimum release year.
-      Takes a full actor name, e.g. "Tom Hanks" and a year e.g 1993 and returns a list of movie titles and release years.
+      Takes an full actor name, e.g. "Tom Hanks" and a year e.g 1993 and returns a list of movie titles and release years.
       Do NOT use this tool with a movie title. Do NOT guess an actor name, Do NOT guess a year.
       A actor name is a fully qualified name with first and last name separated by a space.
       For example, if given "Hanks, Tom" the actor name is "Tom Hanks".

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

@@ -36,7 +36,7 @@ tools:
 ## Reference
 | **field**           | **type**   | **required** | **description**                                                                                 |
 |---------------------|:----------:|:------------:|-------------------------------------------------------------------------------------------------|
-| kind                | string     |     true     | Must be `neo4j-schema`.                                                                         |
+| kind                | string     |     true     | Must be `neo4j-db-schema`.                                                                      |
 | source              | string     |     true     | Name of the source the schema should be extracted from.                                         |
 | description         | string     |     true     | Description of the tool that is passed to the LLM.                                              |
 | cacheExpireMinutes  | integer    |    false     | Cache expiration time in minutes. Defaults to 60.                                               |

docs/en/resources/tools/oceanbase/_index.md

@@ -1,7 +0,0 @@
----
-title: "OceanBase"
-type: docs
-weight: 1
-description: > 
-  Tools that work with OceanBase Sources.
---- 

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

@@ -1,37 +0,0 @@
----
-title: "oceanbase-execute-sql"
-type: docs
-weight: 1
-description: > 
-  An "oceanbase-execute-sql" tool executes a SQL statement against an OceanBase database.
-aliases:
-- /resources/tools/oceanbase-execute-sql
----
-
-## About
-
-An `oceanbase-execute-sql` tool executes a SQL statement against an OceanBase database. It's compatible with the following source:
-
-- [oceanbase](../sources/oceanbase.md)
-
-`oceanbase-execute-sql` takes one input parameter `sql` and runs the sql statement 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.
-
-## Example
-
-```yaml
-tools:
-  execute_sql_tool:
-    kind: oceanbase-execute-sql
-    source: my-oceanbase-instance
-    description: Use this tool to execute sql statement.
-```
-
-## Reference
-
-| **field**   | **type**   | **required** | **description**                                                                                  |
-|-------------|:----------:|:------------:|--------------------------------------------------------------------------------------------------|
-| kind        | string     |     true     | Must be "oceanbase-execute-sql".                                                                 |
-| 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/oceanbase/oceanbase-sql.md

@@ -1,122 +0,0 @@
----
-title: "oceanbase-sql"
-type: docs
-weight: 1
-description: > 
-  An "oceanbase-sql" tool executes a pre-defined SQL statement against an OceanBase database.
-aliases:
-- /resources/tools/oceanbase-sql
----
-
-## About
-
-An `oceanbase-sql` tool executes a pre-defined SQL statement against an OceanBase database. It's compatible with the following source:
-
-- [oceanbase](../sources/oceanbase.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 `?`.
-
-[mysql-prepare]: https://dev.mysql.com/doc/refman/8.4/en/sql-prepared-statements.html
-
-## Example
-
-> **Note:** This tool uses parameterized queries to prevent SQL injections.
-> Query parameters can be used as substitutes for arbitrary expressions.
-> Parameters cannot be used as substitutes for identifiers, column names, table names, or other parts of the query.
-
-```yaml
-tools:
-  search_flights_by_number:
-    kind: oceanbase-sql
-    source: my-oceanbase-instance
-    statement: |
-      SELECT * FROM flights
-      WHERE airline = ?
-      AND flight_number = ?
-      LIMIT 10
-    description: |
-      Use this tool to get information for a specific flight.
-      Takes an airline code and flight number and returns info on the flight.
-      Do NOT use this tool with a flight id. Do NOT guess an airline code or flight number.
-      Example:
-      {{
-          "airline": "CY",
-          "flight_number": "888",
-      }}
-    parameters:
-      - name: airline
-        type: string
-        description: Airline unique 2 letter identifier
-      - name: flight_number
-        type: string
-        description: 1 to 4 digit number
-```
-
-### Example with Template Parameters
-
-> **Note:** This tool allows direct modifications to the SQL statement, 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.
-
-```yaml
-tools:
-  list_table:
-    kind: oceanbase-sql
-    source: my-oceanbase-instance
-    statement: |
-      SELECT * FROM {{.tableName}};
-    description: |
-      Use this tool to list all information from a specific table.
-      Example:
-      {{
-          "tableName": "flights",
-      }}
-    templateParameters:
-      - name: tableName
-        type: string
-        description: Table to select from
-```
-
-### Example with Array Parameters
-
-```yaml
-tools:
-  search_flights_by_ids:
-    kind: oceanbase-sql
-    source: my-oceanbase-instance
-    statement: |
-      SELECT * FROM flights
-      WHERE id IN (?)
-      AND status IN (?)
-    description: |
-      Use this tool to get information for multiple flights by their IDs and statuses.
-      Example:
-      {{
-          "flight_ids": [1, 2, 3],
-          "statuses": ["active", "scheduled"]
-      }}
-    parameters:
-      - name: flight_ids
-        type: array
-        description: List of flight IDs to search for
-        items:
-          name: flight_id
-          type: integer
-          description: Individual flight ID
-      - name: statuses
-        type: array
-        description: List of flight statuses to filter by
-        items:
-          name: status
-          type: string
-          description: Individual flight status
-```
-
-## Reference
-
-| **field**          | **type**                        | **required** | **description**                                                                                                                            |
-|--------------------|:------------------------------:|:------------:|--------------------------------------------------------------------------------------------------------------------------------------------|
-| kind               | string                         |     true     | Must be "oceanbase-sql".                                                                                                                   |
-| 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. | 

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

@@ -19,8 +19,8 @@ database. It's compatible with any of the following sources:
 - [postgres](../../sources/postgres.md)
 
 The specified SQL statement is executed as a [prepared statement][pg-prepare],
-and specified parameters will be inserted according to their position: e.g. `$1`
-will be the first parameter specified, `$2` will be the second parameter, and so
+and specified parameters will inserted according to their position: e.g. `1`
+will be the first parameter specified, `$@` will be the second parameter, and so
 on. If template parameters are included, they will be resolved before execution
 of the prepared statement.
 
@@ -77,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](..#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -107,4 +107,4 @@ tools:
 | description         |                   string                                  |     true     | Description of the tool that is passed to the LLM.                                                                                         |
 | statement           |                   string                                  |     true     | SQL statement to execute on.                                                                                                               |
 | 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. |
+| 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/spanner/spanner-sql.md

@@ -34,8 +34,8 @@ inserted according to their name: e.g. `@name`.
 ### PostgreSQL
 
 For the `postgresql` dialect, the specified SQL statement is executed as a [prepared
-statement][pg-prepare], and specified parameters will be inserted according to
-their position: e.g. `$1` will be the first parameter specified, `$2` will be
+statement][pg-prepare], and specified parameters will inserted according to
+their position: e.g. `$1` will be the first parameter specified, `$@` will be
 the second parameter, and so on.
 
 [pg-prepare]: https://www.postgresql.org/docs/current/sql-prepare.html
@@ -134,7 +134,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](..#template-parameters).
+> [templateParameters](#template-parameters).
 
 ```yaml
 tools:
@@ -165,4 +165,4 @@ tools:
 | statement          |                   string                         |     true     | SQL statement to execute on.                                                                                                               |
 | parameters         | [parameters](../#specifying-parameters)       |    false     | List of [parameters](../#specifying-parameters) that will be inserted into the SQL statement.                                           |
 | readOnly           |                   bool                           |    false     | When set to `true`, the `statement` is run as a read-only transaction. Default: `false`.                                                   |
-| templateParameters | [templateParameters](..#template-parameters) |    false     | List of [templateParameters](..#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
+| templateParameters | [templateParameters](#template-parameters) |    false     | List of [templateParameters](#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |