Tool Implementations
Tools
Architecture
Most of the platform’s low-level runtime routing is handled automatically. What matters in the current UI is how your custom tool is implemented.
The choices you actually make
Section titled “The choices you actually make”Agentic implementation
Section titled “Agentic implementation”Use an Agentic implementation when another workflow agent should fulfill the tool contract for you.
Best for:
- Business logic that is easier to describe as a workflow than as code.
- Tools that should stay inside the platform.
- Cases where you want to orchestrate prompts, phases, and existing platform tools.
Edge implementation
Section titled “Edge implementation”Use an Edge implementation when the tool needs to run close to your infrastructure through an Edge Connector.
Best for:
- On-premise APIs and private-network services.
- System diagnostics and machine-local access.
- Custom integrations that should not run inside the shared platform runtime.
Next steps
Section titled “Next steps” Custom Tools Define a custom tool contract and attach the right implementation.
Edge Connector Use Edge implementations when your tool needs private-network or local-system access.