> 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 Params

> Builder parameters for `tool_call`.

Generated from `cargo doc --no-deps -p nemo-relay -p nemo-relay-adaptive -p nemo-relay-ffi`.

<pre />

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

## Fields

### `name: &'a str`

Tool name recorded on the emitted lifecycle event.

### `args: Json`

Raw tool arguments associated with the span.

### `parent: Option<&'a ScopeHandle>`

Optional explicit parent scope.

### `attributes: ToolAttributes`

Tool attribute bitflags applied to the 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 the start event.

### `tool_call_id: Option<String>`

Optional provider-specific correlation identifier.

### `timestamp: Option<DateTime<Utc>>`

Optional timestamp captured as the handle start time and reused by the emitted start event. When omitted, the current UTC time is used.

## Implementations

### `impl<'a> ToolCallParams<'a>`

<pre />

#### `builder`

<pre />

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