Struct ToolCallPendingConfirmationState 

pub struct ToolCallPendingConfirmationState {
    pub tool_call_id: String,
    pub tool_name: String,
    pub display_name: String,
    pub tool_client_id: Option<String>,
    pub meta: Option<JsonObject>,
    pub invocation_message: StringOrMarkdown,
    pub tool_input: Option<String>,
    pub confirmation_title: Option<StringOrMarkdown>,
    pub edits: Option<AnyValue>,
    pub editable: Option<bool>,
    pub options: Option<Vec<ConfirmationOption>>,
}

Parameters are complete, or a running tool requires re-confirmation (e.g. a mid-execution permission check).

Fields

tool_call_id: String

Unique tool call identifier

tool_name: String

Internal tool name (for debugging/logging)

display_name: String

Human-readable tool name

tool_client_id: Option<String>

If this tool is provided by a client, the clientId of the owning client. Absent for server-side tools.

When set, the identified client is responsible for executing the tool and dispatching session/toolCallComplete with the result.

meta: Option<JsonObject>

Additional provider-specific metadata for this tool call.

Clients MAY look for well-known keys here to provide enhanced UI. For example, a ptyTerminal key with { input: string; output: string } indicates the tool operated on a terminal (both input and output may contain escape sequences).

invocation_message: StringOrMarkdown

Message describing what the tool will do

tool_input: Option<String>

Raw tool input

confirmation_title: Option<StringOrMarkdown>

Short title for the confirmation prompt (e.g. "Run in terminal", "Write file")

edits: Option<AnyValue>

File edits that this tool call will perform, for preview before confirmation

editable: Option<bool>

Whether the agent host allows the client to edit the tool’s input parameters before confirming

options: Option<Vec<ConfirmationOption>>

Options the server offers for this confirmation. When present, the client SHOULD render these instead of a plain approve/deny UI. Each option belongs to a {@link ConfirmationOptionGroup} so the client can still categorise the choices.

Trait Implementations

impl Clone for ToolCallPendingConfirmationState

fn clone(&self) -> ToolCallPendingConfirmationState

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ToolCallPendingConfirmationState

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ToolCallPendingConfirmationState

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ToolCallPendingConfirmationState

fn eq(&self, other: &ToolCallPendingConfirmationState) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for ToolCallPendingConfirmationState

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for ToolCallPendingConfirmationState