Most catalog tools can be inspected without a provider connection. A tool that acts on the human's own provider account may require one at run time.

## The connection sequence

1. `discover` reports whether a candidate requires a connection.
2. `inspect` reports the same state for the selected `tool_id`.
3. If the account is not connected, `run` returns `connection_required` and a `connect_url`.
4. Give that URL to the human and wait for them to approve the provider grant.
5. Inspect the same `tool_id` again, then copy its current worked example before running.

The connection belongs to the account, not to a provider token stored in the agent. Raw provider credentials never enter the agent's prompt or scrollport's application code.

## Teaching errors are part of the contract

An unconnected run should not fail with an opaque provider error. It should say that a connection is required and explain where the human must go. A missing provider permission can still cause a provider-specific error after connection; read the returned `hint` and common errors instead of retrying the same input blindly.

## Keep catalog facts live

Connection status, provider availability, tool schema and pricing can change. This page explains the stable flow only. Browse the [live catalog](https://scrollport.com/tools) and call `inspect` for the current selected tool.