set_data_provider

shallow

io.github.grzesir/botspot-trading · Verify this server

Updates the active conversation to use the specified backtesting data provider. AVAILABILITY AND SETUP: Read these constraints before selecting a provider. Do not probe a provider already declared OFF by calling this tool. Explain its known unavailability and the supported alternatives instead. Preserve the named setup page when explaining a connection requirement. - Theta Data ('theta_data') is OFF right now. Theta Data is not available on BotSpot right now. Never select it and never start a backtest on it. If the user asks for it, say plainly that it is not available and offer the alternatives below. - 'alpaca' uses the user's connected Alpaca broker account for data. Never ask the user to add ALPACA_API_KEY or ALPACA_API_SECRET as environment variables: those names are reserved for broker connections. If Alpaca is not connected or needs reconnecting, send the user to the Broker Connections page. - For OPTIONS: BotSpot Auto has NO options data right now because Theta Data is off, and start_backtest refuses options strategies on 'botspot_auto'. Options backtests need the user's own data: 'alpaca' when the user has a connected Alpaca account (options history from February 2024), or 'polygon' with the user's own POLYGON_API_KEY. Ask the user which one before switching. If they have neither, explain how to connect an Alpaca account (a free one works) or save a Polygon key. BotSpot does not currently have IBKR options support. IMPORTANT: Match the provider to the strategy's asset class requirements. Available providers and their capabilities: - Alpaca (alpaca): stocks, options, crypto - BotSpot Auto (botspot_auto): stocks, options, crypto, futures, indexes - Custom Provider (custom): stocks, options, crypto, futures, indexes - DataBento (databento): futures - Kalshi (kalshi): prediction_contract - Polygon (polygon): stocks, options, crypto, indexes - ProjectX Futures (projectx): futures RULES: - Match the provider to the strategy's asset class requirements - If the strategy requires an asset class the provider doesn't support, STOP and pick a compatible provider - BotSpot Auto is a managed asset-class router. Policy version: 2026-06-26. Current routes: default → ibkr, stock → ibkr, index → ibkr, option → thetadata, crypto → coinbase, crypto_future → coinbase, future → ibkr, cont_future → ibkr. - For STOCKS/INDEXES: Default to 'botspot_auto' (IBKR via router) unless the user explicitly requests a different provider (e.g., 'polygon' or 'alpaca') - For SPOT CRYPTO: Default to 'botspot_auto' (Coinbase via CCXT router) unless the user explicitly requests Polygon/Alpaca for spot crypto - For CRYPTO PERPETUAL/FUTURES: Default to 'botspot_auto' (Coinbase via CCXT router) unless the user explicitly requests a compatible futures provider - For FUTURES: Default to 'botspot_auto' (IBKR via router) unless the user explicitly requests DataBento. If IBKR is missing/unsupported for the requested futures symbol/contract, recommend DataBento as the fallback (BYOK: the user must supply their own DataBento API key). - For a user's saved ProjectX futures connection, select 'projectx-<firm>' (Topstep: 'projectx-topstepx') and its dataConnectionId. History uses that owner's connection; never request reserved broker keys as environment variables. Coverage depends on the provider. - For prediction contracts, select 'kalshi' with the saved Kalshi dataConnectionId. Use that contract's native ticker and YES/NO outcome, not the underlying stock or crypto price. Credentials and demo/live mode come from the saved connection. Historical coverage depends on that environment; do not substitute live data for demo or fabricate missing bars. - If user doesn't have required API keys for a BYOK provider, recommend 'botspot_auto' for stocks, indexes, crypto and futures, or 'custom'. For options, follow the OPTIONS rule above. - The 'custom' provider lets users supply their own data files The tool will return capability validation warnings if there's a mismatch.

100.0/100

1 trials · measured 10 days ago

set_data_provider scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.grzesir/botspot-trading, measured 12 Nov 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-11-12100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: set_data_provider
[![Vouch score](https://vouch.tools/api/tools/d8e3ec0b-e602-4601-a75a-73f096a55a79/badge.svg)](https://vouch.tools/tools/d8e3ec0b-e602-4601-a75a-73f096a55a79)
set_data_provider — Vouch