Tool Args
Where a tool’s body starts. It runs when the Tool’s trigger fires (the model called the tool): it reads call, splits it into one output per argument and fires trigger to run the rest of the body. Its field names are also the tool’s parameters (in auto mode the Tool builds its schema from them). Wire the body’s answer back into the Tool’s result and its trigger into result_trigger.
Fired. It runs when an event lands on trigger, and pulls its other inputs at that moment. A data wire never fires it.
Inputs
Section titled “Inputs”| Port | Type | Notes |
|---|---|---|
trigger |
event | Fires the node |
call |
tool-call |
Outputs
Section titled “Outputs”| Port | Type | Notes |
|---|---|---|
trigger |
event |
Right-click a knob and pick Convert to input to drive it from a wire.
| Knob | Kind | Default | Notes |
|---|---|---|---|
fieldsArguments |
text | empty | placeholder location, unit |
Example
Section titled “Example”The start of a tool’s branch. Type the arguments the model should send, city, unit, and the node grows one output per argument; in the Tool’s auto mode they are also the tool’s parameters. Wire the Tool’s trigger into trigger and its call into call. When the model calls the tool, trigger fires, each argument arrives on its own wire (a missing one is empty), and trigger fires the rest of the branch.