List saved broker credentials
list_broker_credentialsLists saved broker credential metadata for the authenticated user. Raw credential values are never returned. Use an item's id as start_deployment.brokerCredentialId only when the user explicitly named that exact saved broker connection/account for this deployment. If no matching credential exists, call broker_connections(action="connect_existing") only when the user asks to create one. Returned metadata includes broker, displayName, paperOrLive, accountDisplay, keyNames, status, timestamps, brokerDataExecution, and one recommendedForReadOnlyAnalysis marker when an eligible connection exists. Interactive Brokers credentials are never eligible for isolated analysis or graphing; that data source is reserved for the separate backtesting path. All supported broker-data operations execute through the LumiBot adapter selected by the saved connection. For an ordinary read-only request where the user did not name an account, use the exact id of the item marked recommendedForReadOnlyAnalysis=true. Use another active item's exact id only when the user named that saved connection and it is not Interactive Brokers. accountDisplay is a safe label such as 'Account ending in 4821'; never infer an account suffix from the brokerCredentialId UUID. The tool never includes full account numbers, raw keys, Vault secret ids, or broker account secrets. connectionStatus explains whether the connection is usable, reconnectRecommended tells the Agent whether the user must reconnect, and connectionUpdatedAt is the latest safe renewal or connection update time. backtestData reports, for each asset class, the data source a backtest would use now, whether the user must link their own connection or key first, which ones qualify with this user's status for each, the first day of history when it is limited, and the next step. Read it before promising or starting a backtest that may need the user's own data. For a named broker, use brokerProvider; for one exact saved connection, use brokerCredentialId. These optional filters scope both returned items and recovery actions. An unrelated active account cannot suppress recovery for the selected connection. When no selected account is active and at least one item status is reconnect_required, the structured result includes a reconnect_broker recovery action. If any account is active, no global connection recovery action is returned; use an active account matching the requested broker and treat stale account statuses individually. Empty credentials return a connect_broker action. Present the returned action.message directly: identify the affected broker, explain that access is unavailable because its connection needs reconnecting, and provide the returned recovery action. BotSpot chat renders these structured actions as cards. Codex, Claude, Cursor, and other clients without native BotSpot cards must present the exact returned action.url as a clickable Markdown link; never refer to a card that the client did not render. Do not use a reconnect_required item for broker data, place_trade, or start_deployment until the user reconnects it. For a broker or exchange API key used to trade, tell the user to enable trading. Before setup or replacement, give this warning only when the broker offers those permissions separately: Warning. Only turn on trading permissions. Leave deposits and withdrawals off. Use the broker’s actual settings. If a broker bundles transfers with trading, explain that when relevant and keep trading available. Never ask the user to paste credentials into chat. For interactive setup or replacement, send the user to BotSpot Broker Connections (/account-settings/broker-connections) to enter the key there.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_broker_credentials"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| brokerProvider | No | ||
| brokerCredentialId | No |