Class: TemporalMCPToolset
googleAdkAgentsWorkflow.TemporalMCPToolset
A BaseToolset whose MCP traffic is durable under Temporal.
Hierarchy
-
BaseToolset↳
TemporalMCPToolset
Constructors
constructor
• new TemporalMCPToolset(options): TemporalMCPToolset
Parameters
| Name | Type | Description |
|---|---|---|
options | TemporalMCPToolsetOptions | Toolset configuration. name selects the worker-side factory and names the backing Activities. |
Returns
Overrides
BaseToolset.constructor
Properties
[BASE_TOOLSET_SIGNATURE_SYMBOL]
• Readonly [BASE_TOOLSET_SIGNATURE_SYMBOL]: true
Inherited from
BaseToolset.[BASE_TOOLSET_SIGNATURE_SYMBOL]
prefix
• Optional Readonly prefix: string
Inherited from
BaseToolset.prefix
toolFilter
• Readonly toolFilter: string[] | ToolPredicate
Inherited from
BaseToolset.toolFilter
Methods
close
▸ close(): Promise<void>
No-op: the workflow-side toolset holds no MCP session to close.
Returns
Promise<void>
Overrides
BaseToolset.close
getTools
▸ getTools(context?): Promise<BaseTool[]>
Discovers the server's tools. Inside a Workflow this proxies the
<name>-listTools Activity and wraps each returned declaration in a
workflow-side TemporalMCPTool; outside a Workflow it delegates to a
real MCPToolset built from connectionParams.
Parameters
| Name | Type |
|---|---|
context? | ReadonlyContext |
Returns
Promise<BaseTool[]>
Overrides
BaseToolset.getTools
processLlmRequest
▸ processLlmRequest(toolContext, llmRequest): Promise<void>
Processes the outgoing LLM request for this toolset. This method will be called before each tool processes the llm request.
Use cases:
- Instead of let each tool process the llm request, we can let the toolset process the llm request. e.g. ComputerUseToolset can add computer use tool to the llm request.
Parameters
| Name | Type | Description |
|---|---|---|
toolContext | Context | The context of the tool. |
llmRequest | LlmRequest | The outgoing LLM request, mutable this method. |
Returns
Promise<void>
Inherited from
BaseToolset.processLlmRequest