ProviderTool | TanStack AI Tiếng Việt

Defined in: packages/ai/src/tools/provider-tool.ts:19

A provider-specific tool produced by an adapter-package factory (e.g. webSearchTool from @tanstack/ai-anthropic/tools).

The two ~-prefixed fields are type-only phantom brands — they are never assigned at runtime. They allow the core type system to match a factory's output against the selected model's supports.tools list and surface a compile-time error when the combination is unsupported.

User-defined tools (via toolDefinition()) remain plain Tool and stay assignable to any model.

Extends

Tool

Type Parameters

TProvider

TProvider extends string

Provider identifier (e.g. 'anthropic', 'openai').

TKind

TKind extends string

Canonical tool-kind string matching the provider's supports.tools entries (e.g. 'web_search', 'code_execution').

Properties

~provider

readonly ~provider: TProvider;

Defined in: packages/ai/src/tools/provider-tool.ts:23

~toolKind

readonly ~toolKind: TKind;

Defined in: packages/ai/src/tools/provider-tool.ts:24

description

description: string;

Defined in: packages/ai/src/types.ts:980

Clear description of what the tool does.

This is crucial - the model uses this to decide when to call the tool. Be specific about what the tool does, what parameters it needs, and what it returns.

Example

"Get the current weather in a given location. Returns temperature, conditions, and forecast."

Inherited from

Tool.description

execute?

optional execute?: (args, context?) => any;

Defined in: packages/ai/src/types.ts:1060

Optional function to execute when the model calls this tool.

If provided, the SDK will automatically execute the function with the model's arguments and feed the result back to the model. This enables autonomous tool use loops.

Can return any value - will be automatically stringified if needed.

Parameters

args

any

The arguments parsed from the model's tool call (validated against inputSchema)

context?

ToolExecutionContext<unknown>

Returns

any

Result to send back to the model (validated against outputSchema if provided)

Example

execute: async (args) => {
  const weather = await fetchWeather(args.location);
  return weather; // Can return object or string
}

Inherited from

Tool.execute

inputSchema?

optional inputSchema?: SchemaInput;

Defined in: packages/ai/src/types.ts:1020

Schema describing the tool's input parameters.

Can be any Standard JSON Schema compliant schema (Zod, ArkType, Valibot, etc.) or a plain JSON Schema object. Defines the structure and types of arguments the tool accepts. The model will generate arguments matching this schema. Standard JSON Schema compliant schemas are converted to JSON Schema for LLM providers.

See

Examples

// Using Zod v4+ schema (natively supports Standard JSON Schema)
import { z } from 'zod';
z.object({
  location: z.string().describe("City name or coordinates"),
  unit: z.enum(["celsius", "fahrenheit"]).optional()
})

// Using ArkType (natively supports Standard JSON Schema)
import { type } from 'arktype';
type({
  location: 'string',
  unit: "'celsius' | 'fahrenheit'"
})

// Using plain JSON Schema
{
  type: 'object',
  properties: {
    location: { type: 'string', description: 'City name or coordinates' },
    unit: { type: 'string', enum: ['celsius', 'fahrenheit'] }
  },
  required: ['location']
}

Inherited from

Tool.inputSchema

lazy?

optional lazy?: boolean;

Defined in: packages/ai/src/types.ts:1066

If true, this tool is lazy and will only be sent to the LLM after being discovered via the lazy tool discovery mechanism. Works with both chat() (the synthetic discovery tool) and Code Mode (kept out of the system prompt and revealed via discover_tools).

Inherited from

Tool.lazy

metadata?

optional metadata?: Record<string, any>;

Defined in: packages/ai/src/types.ts:1077

Additional metadata for adapters or custom extensions

Inherited from

Tool.metadata

name

name: string;

Defined in: packages/ai/src/types.ts:970

Unique name of the tool (used by the model to call it).

Should be descriptive and follow naming conventions (e.g., snake_case or camelCase). Must be unique within the tools array.

Example

"get_weather", "search_database", "sendEmail"

Inherited from

Tool.name

needsApproval?

optional needsApproval?: boolean;

Defined in: packages/ai/src/types.ts:1063

If true, tool execution requires user approval before running. Works with both server and client tools.

Inherited from

Tool.needsApproval

outputSchema?

optional outputSchema?: SchemaInput;

Defined in: packages/ai/src/types.ts:1041

Optional schema for validating tool output.

Can be any Standard JSON Schema compliant schema or a plain JSON Schema object. If provided with a Standard Schema compliant schema, tool results will be validated against this schema before being sent back to the model. This catches bugs in tool implementations and ensures consistent output formatting.

Note: This is client-side validation only - not sent to LLM providers. Note: Plain JSON Schema output validation is not performed at runtime.

Example

// Using Zod
z.object({
  temperature: z.number(),
  conditions: z.string(),
  forecast: z.array(z.string()).optional()
})

Inherited from

Tool.outputSchema

replay?

optional replay?: "safe" | "never";

Defined in: packages/ai/src/types.ts:1074

Whether a host may run this tool again after a crash cut the run between the call and its result. 'safe' runs it again. Omit the field, or set 'never', when a second run is not safe. The host writes the model note. chat() does not read this field.

Inherited from

Tool.replay