docs: migration of core package samples from go sdk #2330

AnmolShukla2002 · 2026-01-19T09:20:11Z

This PR migrates the Go SDK documentation and core technical samples from the [mcp-toolbox-sdk-go] repository to the main genai-toolbox documentation site. This consolidation ensures that conceptual guides, package overviews, and interactive code examples are available in a centralized "one-stop-shop".

gemini-code-assist · 2026-01-19T09:20:29Z

Summary of Changes

Hello @AnmolShukla2002, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the documentation for the MCP Toolbox Go SDK's core package. It provides developers with a centralized and comprehensive resource for understanding the SDK's capabilities, from basic setup and tool interaction to advanced topics like secure authentication mechanisms and flexible parameter binding. Furthermore, it offers ready-to-use integration samples for leading AI orchestration frameworks, streamlining the development of intelligent applications using the Toolbox.

Highlights

Comprehensive Go SDK Documentation: Introduces a new, detailed documentation page for the MCP Toolbox Go SDK's core package, covering installation, usage, and advanced features.
Authentication Guides: Provides in-depth guidance on both client-to-server authentication (e.g., for Cloud Run deployments) and tool-level authentication, including token retrieval and configuration options.
Parameter Binding Functionality: Explains how to bind static or dynamic values to tool parameters, enhancing security and control over tool invocation.
Orchestration Framework Integration Samples: Includes practical code examples demonstrating how to integrate the Go SDK with popular AI orchestration frameworks like Google GenAI, LangChain Go, and OpenAI Go.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request adds extensive documentation and samples for the Go SDK core package. The documentation is comprehensive, but I've found several issues in the code samples, including incomplete examples, incorrect API usage, unhandled errors, and typos. These issues could confuse users or cause their code to fail if they copy the examples. I've left specific comments with suggestions for fixes. Addressing these will greatly improve the quality and usability of the documentation.

docs/en/sdks/go-sdk/core/_index.md

gemini-code-assist · 2026-01-19T09:22:51Z

docs/en/sdks/go-sdk/core/_index.md

+
+
+```go
+import "github.com/googleapis/mcp-toolbox-sdk-go/core"


This code example is incomplete as it uses the oauth2 package without importing it. Please add the import for golang.org/x/oauth2 to make the example runnable.

Suggested change

import "github.com/googleapis/mcp-toolbox-sdk-go/core"

import (

"github.com/googleapis/mcp-toolbox-sdk-go/core"

"golang.org/x/oauth2"

)

gemini-code-assist · 2026-01-19T09:22:51Z

docs/en/sdks/go-sdk/core/_index.md

+    token, err := core.GetGoogleIDToken(ctx, URL)
+
+    client, err := core.NewToolboxClient(
+      URL,
+      core.WithClientHeaderString("Authorization", token),


This code snippet has a couple of issues:

The URL variable is used but not defined. It should be replaced with a placeholder to make it clear to the user.

The Authorization header for a bearer token should be in the format "Bearer <token>". The current example is missing the "Bearer " prefix, which will lead to authentication failures.

Suggested change

token, err := core.GetGoogleIDToken(ctx, URL)

client, err := core.NewToolboxClient(

URL,

core.WithClientHeaderString("Authorization", token),

token, err := core.GetGoogleIDToken(ctx, "your-cloud-run-url")

client, err := core.NewToolboxClient(

"your-cloud-run-url",

core.WithClientHeaderString("Authorization", "Bearer "+token),

gemini-code-assist · 2026-01-19T09:22:51Z

docs/en/sdks/go-sdk/core/_index.md

+tool, err := client.LoadTool("my-tool", ctx)
+
+AuthTool, err := tool.ToolFrom(
+  core.WithAuthTokenSource("my-auth", headerTokenSource),


This code example is incomplete. The headerTokenSource variable is used in core.WithAuthTokenSource but it is not defined anywhere in the snippet. Please define it to make the example complete and runnable for users.

gemini-code-assist · 2026-01-19T09:22:51Z

docs/en/sdks/go-sdk/core/_index.md

+				log.Fatal("Could not invoke tool", err)
+			}
+
+			params.Messages = append(params.Messages, openai.ToolMessage(result.(string), toolCall.ID))


The type assertion result.(string) is unsafe and will cause a panic if the result from tool.Invoke is not a string. The Invoke method returns any, so its type is not guaranteed. It's safer to convert the result to a string using fmt.Sprintf to avoid a panic.

Suggested change

params.Messages = append(params.Messages, openai.ToolMessage(result.(string), toolCall.ID))

params.Messages = append(params.Messages, openai.ToolMessage(fmt.Sprintf("%v", result), toolCall.ID))

docs/en/sdks/go-sdk/core/_index.md

gemini-code-assist · 2026-01-19T09:22:52Z

docs/en/sdks/go-sdk/core/_index.md

+	// Make initial chat completion request
+	completion, err := openAIClient.Chat.Completions.New(ctx, params)
+	if err != nil {
+		panic(err)


This example uses panic(err) for error handling, which is generally discouraged in Go applications unless it's a truly unrecoverable state during initialization. It's also inconsistent with other parts of the example that use log.Fatal. Using log.Fatalf would be more idiomatic and consistent for a main function.

Suggested change

panic(err)

log.Fatalf("Chat completion failed: %v", err)

docs/en/sdks/go-sdk/core/_index.md

github-actions · 2026-01-19T09:24:12Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

anubhav756

Can we have major sections added as separate pages under the SDKs' sections?

anubhav756 · 2026-01-19T10:02:05Z

There seem to be links to the READMEs of individual packages in the top-level doc (screenshot). Can we have them linked to this docsite?

docs/en/sdks/go-sdk/core/_index.md

github-actions · 2026-01-29T10:20:13Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

github-actions · 2026-01-29T10:49:18Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

AnmolShukla2002 · 2026-01-29T10:57:17Z

There seem to be links to the READMEs of individual packages in the top-level doc (screenshot). Can we have them linked to this docsite?

I guess docs reorganization strategy states that we will "treat each SDK repository as the source of truth for its own API reference". While the docsite serves as the "one-stop-shop" for conceptual guides, the github links serve as the technical reference point until our auto-generated API subdomains are fully live. I am not sure on this, let me know your thoughts?

anubhav756 · 2026-01-29T12:39:30Z

There seem to be links to the READMEs of individual packages in the top-level doc (screenshot). Can we have them linked to this docsite?

I guess docs reorganization strategy states that we will "treat each SDK repository as the source of truth for its own API reference". While the docsite serves as the "one-stop-shop" for conceptual guides, the github links serve as the technical reference point until our auto-generated API subdomains are fully live. I am not sure on this, let me know your thoughts?

Sounds good! Let’s link directly to the github source files until we have the API ref docsite up.

However for links like those under “Which package should I use?”, I guess I was assuming the links from core, tbadk and tbgenkit could be linked to the packages’ respective pages to the guidance docs that I assume we would be adding to the main docsite (just like we have done for the core package). Currently they seem to link to the github source code (unless it’s intentional because I see the core package guidance page is linked at the bottom of that page, but just thinking what if we also link the guidance pages in that section as well). Thoughts?

anubhav756

LGTM, given we address the bot comments and link checker error as well. Optionally, adding a PR description might help as well.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

github-actions · 2026-01-30T05:08:03Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

AnmolShukla2002 · 2026-01-30T08:45:53Z

There seem to be links to the READMEs of individual packages in the top-level doc (screenshot). Can we have them linked to this docsite?

I guess docs reorganization strategy states that we will "treat each SDK repository as the source of truth for its own API reference". While the docsite serves as the "one-stop-shop" for conceptual guides, the github links serve as the technical reference point until our auto-generated API subdomains are fully live. I am not sure on this, let me know your thoughts?

Sounds good! Let’s link directly to the github source files until we have the API ref docsite up.

However for links like those under “Which package should I use?”, I guess I was assuming the links from core, tbadk and tbgenkit could be linked to the packages’ respective pages to the guidance docs that I assume we would be adding to the main docsite (just like we have done for the core package). Currently they seem to link to the github source code (unless it’s intentional because I see the core package guidance page is linked at the bottom of that page, but just thinking what if we also link the guidance pages in that section as well). Thoughts?

yes made these changes!

AnmolShukla2002 · 2026-01-30T08:47:49Z

LGTM, given we address the bot comments and link checker error as well. Optionally, adding a PR description might help as well.

Bot's comments are mostly regarding the sample...I am not sure If I should make these changes as it would then defer from the sample in the Sdk repos?

github-actions · 2026-01-30T08:48:25Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

docs/en/sdks/go-sdk/core/_index.md

anubhav756 · 2026-02-02T12:25:29Z

docs/en/sdks/go-sdk/_index.md


    Before using the SDKs, you need the MCP Toolbox server running. Follow
    the instructions here: [**Toolbox Getting Started
    Guide**](https://github.com/googleapis/genai-toolbox?tab=readme-ov-file#getting-started)


Should we update links like these to also point to the main docsite now that we have migrated all the SDKs guidance as well?

Once these sub branches are merged I will update all the links

anubhav756 · 2026-02-02T12:32:15Z

docs/en/sdks/go-sdk/core/_index.md

+Closing the `ToolboxClient` also closes the underlying network session shared by all tools loaded from that client. As a result, any tool instances you have loaded will cease to function and will raise an error if you attempt to invoke them after the client is closed.
+{{< /notice >}}
+
+## Transport Protocols


Similar to my comment from some of the previous PRs, can we have all the major sections from this guide broken into multiple pages in the menu?

This might make the docs a bit more intuitive and easier to read and share.

WDYT?

I suggest we maintain the single-page structure to make sure a cohesive experience for developers during the setup phase. Breaking down these readmes into separate pages for every minor technical section would create content fragments that lack the necessary "big-picture" context.....requiring a user to read 17 other documents just to understand a single proposal. This approach keeps the navigation sidebar clean and focused on our three core package offerings Core, TBADK, and TBGenkit rather than cluttering the menu with excessive sub-levels that can overwhelm both developers and reviewers. By making this sure we are allowing readers to scan through the document quickly to understand what the package represents and how to use it efficiently.

docs/en/sdks/go-sdk/core/_index.md

Co-authored-by: Anubhav Dhawan <[email protected]>

github-actions · 2026-02-03T09:25:22Z

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-2330/

docs: migration of core package samples from go sdk

c72e205

AnmolShukla2002 requested a review from a team as a code owner January 19, 2026 09:20

blunderbuss-gcf bot assigned Yuan325 Jan 19, 2026

AnmolShukla2002 assigned AnmolShukla2002 and unassigned Yuan325 Jan 19, 2026

AnmolShukla2002 requested review from anubhav756 and dishaprakash January 19, 2026 09:21

gemini-code-assist bot reviewed Jan 19, 2026

View reviewed changes

AnmolShukla2002 mentioned this pull request Jan 19, 2026

docs: migration of Go Sdk docs #2292

Open

anubhav756 reviewed Jan 19, 2026

View reviewed changes

anubhav756 requested changes Jan 19, 2026

View reviewed changes

docs/en/sdks/go-sdk/core/_index.md Outdated Show resolved Hide resolved

docs/en/sdks/go-sdk/core/_index.md Outdated Show resolved Hide resolved

docs/en/sdks/go-sdk/core/_index.md Outdated Show resolved Hide resolved

refactored sample section

aa121e1

align docsy/hugo theme for tags

8e4cd41

anubhav756 approved these changes Jan 29, 2026

View reviewed changes

Update docs/en/sdks/go-sdk/core/_index.md

569b988

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

update framework links to docsite

a49191f

anubhav756 approved these changes Feb 2, 2026

View reviewed changes

anubhav756 self-requested a review February 2, 2026 12:30

anubhav756 requested changes Feb 2, 2026

View reviewed changes

docs/en/sdks/go-sdk/core/_index.md Outdated Show resolved Hide resolved

Update docs/en/sdks/go-sdk/core/_index.md

4ff4466

Co-authored-by: Anubhav Dhawan <[email protected]>

	params.Messages = append(params.Messages, openai.ToolMessage(result.(string), toolCall.ID))
	params.Messages = append(params.Messages, openai.ToolMessage(fmt.Sprintf("%v", result), toolCall.ID))

docs: migration of core package samples from go sdk #2330

Are you sure you want to change the base?

docs: migration of core package samples from go sdk #2330

Uh oh!

Conversation

AnmolShukla2002 commented Jan 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gemini-code-assist bot commented Jan 19, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

gemini-code-assist bot Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

gemini-code-assist bot Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Jan 19, 2026

Uh oh!

anubhav756 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

anubhav756 commented Jan 19, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Jan 29, 2026

Uh oh!

github-actions bot commented Jan 29, 2026

Uh oh!

AnmolShukla2002 commented Jan 29, 2026

Uh oh!

anubhav756 commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anubhav756 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

AnmolShukla2002 commented Jan 30, 2026

Uh oh!

AnmolShukla2002 commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

Uh oh!

anubhav756 Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

AnmolShukla2002 Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

anubhav756 Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

AnmolShukla2002 Feb 3, 2026

AnmolShukla2002 commented Jan 19, 2026 •

edited

Loading

anubhav756 left a comment •

edited

Loading

anubhav756 commented Jan 29, 2026 •

edited

Loading

anubhav756 left a comment •

edited

Loading