Bind and validate tools¶
After configuring a tool, open the target agent’s details and add it in the tools section. Search, select, save, and check the binding list. Where an instance is required, select the intended connection using the available configuration entry.
Test a specific task¶
Tool type |
Example test |
Verify |
|---|---|---|
Search |
Find a public product document and cite it |
Search call and accessible source links |
GitHub |
Read recent issues in a specified test repository |
Repository, issue content, and links |
Monitoring or cluster |
Read a specified test resource |
The resource in the target system |
Email or messaging |
Send to a test recipient after confirming the target and content |
Actual receipt at the destination |
Event callback |
Generate a test event in the source system |
Delivery, reception, and execution by the correct target |
Check target-system permissions first. For outbound tests, explicitly identify the recipient and content so you do not accidentally use a real business recipient.
Inspect calls¶
Review tool records in the conversation. Enable developer mode if needed to inspect the name, parameters, and response. Mentioning a platform in an answer does not prove that the agent called it.
If the expected tool was not used, check agent bindings and connections, then prompt or skill restrictions on external calls. Configuring a search provider’s key does not mean every question will invoke that provider.
Unbind¶
Unbind a tool in agent details to stop that assistant from using it. To disable a connection or rotate credentials, see Tool maintenance.