> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/relay/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo/relay/_mcp/server.

# Struct Tool Call Execute Params

> Builder parameters for `tool_call_execute`.

Generated from `cargo doc --no-deps -p nemo-relay -p nemo-relay-adaptive -p nemo-relay-pii-redaction -p nemo-relay-ffi -p nemo-relay-types -p nemo-relay-plugin -p nemo-relay-worker-proto -p nemo-relay-worker`.

<pre />

Builder parameters for [`tool_call_execute`](/reference/api/rust-library-reference/nemo-relay/api/tool/fn-tool-call-execute).

## Fields

### `name: String`

Tool name recorded on emitted lifecycle events.

### `args: Json`

Raw tool arguments passed into the managed pipeline.

### `func: ToolExecutionNextFn`

Tool callback or execution continuation.

### `parent: Option<ScopeHandle>`

Optional explicit parent scope for the emitted tool span.

### `attributes: ToolAttributes`

Tool attribute bitflags applied to the managed span.

### `data: Option<Json>`

Optional application payload stored on the handle but not emitted as Agent Trajectory Observability Format (ATOF) data.

### `metadata: Option<Json>`

Optional JSON metadata recorded on emitted events.

### `tool_call_id: Option<String>`

Optional provider-specific correlation identifier.

## Implementations

### `impl ToolCallExecuteParams`

<pre />

#### `builder`

<pre />

Create a builder for building `ToolCallExecuteParams`. On the builder, call `.name(...)`, `.args(...)`, `.func(...)`, `.parent(...)`(optional), `.attributes(...)`(optional), `.data(...)`(optional), `.metadata(...)`(optional), `.tool_call_id(...)`(optional) to set the values of the fields. Finally, call `.build()` to create the instance of `ToolCallExecuteParams`.