Inspect connections and instances¶
Open the marketplace tool and determine whether it uses a search-credential form or instance management. The fields differ; search tools do not use instance names in the same way.
Search credentials¶
Bocha and Tavily require an API Key. Brave requires a Subscription Token. Existing configurations provide actions to test the connection, replace credentials, or delete them. Complete keys are not displayed after saving; check status and test results.
Instance lists¶
Instances maintain different connections for the same tool. The list shows the instance name, status, latest check, and actions. Use the controls on the intended row to test, view, edit, or disconnect it.
For example, GitHub repository API access and Webhook callbacks serve different purposes. An Access Token and a Webhook Secret are not interchangeable. Name communication applications, robots, and mailbox connections separately.
Interpret status correctly¶
Status or action |
What it establishes |
What still needs checking |
|---|---|---|
Configuration saved |
Parameters were submitted and can be read again |
Valid credentials and service availability |
Connection test succeeded |
The interfaces covered by that test are reachable |
Permissions for the intended action and actual business result |
Latest check time |
A connection was checked at that time |
Subsequent credential changes or expiry |
Tool bound |
The capability is in the assistant’s configuration |
Whether this task invoked it and whether the result is correct |
Review the tool-specific fields, then validate an actual invocation.