> ISPO SDK documentation. [HTML](https://ispo.ai/docs/interfaces/core.PromptToolCall.html) · [Documentation index](https://ispo.ai/docs/llms.txt)

# Interface PromptToolCall

One tool invocation recorded on a message. The provider's own call id is the join key to the matching [PromptToolResult](core.PromptToolResult.md); a store that omits it leaves `id` absent rather than inventing one, because positional pairing is wrong the moment a turn issues parallel calls.

```typescript
interface PromptToolCall {
    id?: string;
    name: string;
}
```

Types: [id](#id), [name](#name)

##### Index

### <a id="properties"></a>Properties

[id?](#id) [name](#name)

## <a id="properties-1"></a>Properties

### <a id="id"></a>`Optional`id

```typescript
id?: string
```

Provider call id (`toolu_…` / `call_…`). Absent when the store omits it.

### <a id="name"></a>name

```typescript
name: string
```

Exact tool name as invoked, e.g. `mcp__ispo-host__get_project_context`.