Static variables and aliases
Inject server-controlled values into tool calls without LLM involvement, and chain values across tool calls deterministically
Vapi tools support two features that let you move data between tool calls deterministically, without relying on the LLM to interpret or forward values:
- Static variables (parameters) inject fixed or template-resolved values into every tool call, regardless of what the LLM generates.
- Variable extraction (aliases) pull specific fields out of a tool’s JSON response and store them for use in subsequent tool calls.
Combined, these features enable deterministic tool chaining — Tool A fetches data and extracts variables, Tool B receives those variables automatically. The LLM orchestrates when tools run, but the data flow between them is fully controlled by you.
The four pages in this section cover each mechanism in turn, then the failure modes that come up most often.
In this section
Next steps
Now that you understand static variables and aliases:
- Passing data between assistants: Choose the right primitive for forwarding context across handoffs in a squad.
- Function tools: Learn how to create and configure Function tools.
- Tool rejection plan: Add conditions to prevent unintended tool calls.
- API reference: See the complete tool creation API reference.