If your agent says it has no Signl tools, the connection is not active in that conversation. The cause is nearly always one of four things: authorization was never completed, you are in a different workspace than the one you connected, the client has a stale tool list, or the credential was revoked. Work through them in that order.
1. Confirm the connector is authorized
Adding a connector and authorizing it are separate steps. In your client's connector settings, check that Signl shows as connected rather than merely listed. If it is pending, run the authorization again and complete the browser step.
2. Check which workspace or project you are in
Connectors are usually scoped. A connector added in one workspace, project or custom assistant will not appear in another. Confirm the conversation you are testing in belongs to the same scope where you added Signl.
3. Restart the client
Clients cache the tool list from when the connection was established. If you added Signl mid-session, quit and reopen the app so it fetches the current list.
4. Verify the credential still works
If you used an API key, confirm it has not been revoked: open API Key in the dashboard and check it is still listed as active. Revoked keys fail authentication silently from the agent's point of view. Generate a new one if needed, remembering the key is shown only once.
Still not working
Ask the agent directly what it can see:
List every tool you have access to right now.If Signl's tools are absent from that list, the problem is the connection rather than the agent's reasoning. Re-add the connector from scratch using the steps in connect your agent, and email vlad@akyx.digital if it persists.