From 4c96bb5c813045ac2b7175c69281589b3bab26db Mon Sep 17 00:00:00 2001 From: Averi Kitsch Date: Mon, 2 Feb 2026 11:13:55 -0800 Subject: [PATCH 1/2] docs: fix dataplex tool names in reference (#2366) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## 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/genai-toolbox/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 # --- docs/en/reference/prebuilt-tools.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/reference/prebuilt-tools.md b/docs/en/reference/prebuilt-tools.md index bf7013f902..d8a2e806b3 100644 --- a/docs/en/reference/prebuilt-tools.md +++ b/docs/en/reference/prebuilt-tools.md @@ -414,10 +414,10 @@ See [Usage Examples](../reference/cli.md#examples). 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 + * `search_entries`: Searches for entries in Dataplex Catalog. + * `lookup_entry`: Retrieves a specific entry from Dataplex Catalog. - * `dataplex_search_aspect_types`: Finds aspect types relevant to the + * `search_aspect_types`: Finds aspect types relevant to the query. ## Firestore From eef7a94977fcffbba920ce390816d092a20372a2 Mon Sep 17 00:00:00 2001 From: Yuan Teoh <45984206+Yuan325@users.noreply.github.com> Date: Mon, 2 Feb 2026 17:38:15 -0800 Subject: [PATCH 2/2] docs: close notice shortcode (#2404) fix notice shortcode closing brackets. --- docs/en/how-to/invoke_tool.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/en/how-to/invoke_tool.md b/docs/en/how-to/invoke_tool.md index c144be96c6..7448de13fa 100644 --- a/docs/en/how-to/invoke_tool.md +++ b/docs/en/how-to/invoke_tool.md @@ -13,12 +13,12 @@ The `invoke` command allows you to invoke tools defined in your configuration di {{< notice tip >}} **Keep configurations minimal:** The `invoke` command initializes *all* resources (sources, tools, etc.) defined in your configuration files during execution. To ensure fast response times, consider using a minimal configuration file containing only the tools you need for the specific invocation. -{{< notice tip >}} +{{< /notice >}} -## Prerequisites +## Before you begin -- You have the `toolbox` binary installed or built. -- You have a valid tool configuration file (e.g., `tools.yaml`). +1. Make sure you have the `toolbox` binary installed or built. +2. Make sure you have a valid tool configuration file (e.g., `tools.yaml`). ## Basic Usage