agenthub · tool.call
Tool Call
Invoke a registered tool through the gateway at a fixed point in the graph. Deterministic — the graph decides when it runs, not the model.
Why the node earns its place
The node names the tool and the parameters; the gateway resolves credentials per caller, decrypts them and dispatches. No secret ever sits on the canvas, and identity propagates, so the same node reads the publisher's connection while building and the buyer's own connection at runtime.
It emits one output port carrying the whole gateway envelope rather than four typed ports. The node no longer decides how to project the response — the graph does, with paths.
How it works at run time
- 1Forward the caller's identity and the wired params to the gateway for the configured tool.
- 2The gateway handles credential decryption, dispatch and any subscription gate.
- 3Return the whole envelope on one port: ok, result, error, and per-leg costs.
What comes out
output.ok did it succeed
output.result the tool's result, e.g. {status_code, body}
output.error {code, message} on failure
output.leg_costs per-leg cost attributionWhat you wire
Inputs
- params *object
Outputs
- outputobject
Configuration
| Key | Type | Default & options | What it does |
|---|---|---|---|
| tool_id * | string | — | Stable tool identifier from auth_layer's registry (e.g. 'notion', 'candidate_evaluator'). |
What usually goes wrong
Watch for this
Navigate the envelope with paths — a Condition on output.ok, a transform into output.result.body.results. A failure is reported as ok: false rather than raised, so a graph that never checks ok will happily carry an error object into a model.
Behaviour & provenance