OptionContext
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTAPI_BASE_URL | No | Alternative base URL used in local or custom API gateway environments. If OPTIONCONTEXT_BASE_URL is omitted, this will be used as fallback. | |
| OPTIONCONTEXT_API_KEY | Yes | Your Agent-as-a-Service API key. | |
| OPTIONCONTEXT_BASE_URL | No | The OptionContext endpoint gateway URL (defaults to https://mcp.optioncontext.com if omitted). | https://mcp.optioncontext.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_agent_infoA | Fetch information about the current Agent API key, including plan type, active status, remaining credits, and symbol access limits. Args: api_key (str, optional): Override API Key. If omitted, uses environment key. |
| suggest_symbolsA | Search and resolve correct ticker symbols (e.g. searching 'Reliance' to get 'RELIANCE'). Args: query (str): The search text or company name. |
| get_market_contextA | Fetch live quote details, last traded price (LTP), volume, and context for Stocks, Indices, and Futures. Args: symbol (str): Ticker symbol (e.g. 'NIFTY', 'BANKNIFTY', 'RELIANCE'). expiry (str): Expiry cycle ('SPOT', 'NEAR', 'FAR', 'NEXT'). Default is 'SPOT'. asset_type (str): Asset category ('stock', 'index', 'future', 'auto'). Default is 'auto'. api_key (str, optional): API Key. If omitted, uses OPTIONCONTEXT_API_KEY from environment. |
| get_option_chainA | Fetch complete option chain matrix including PCR, ATM strike, CE/PE quotes, volume, and Greeks. Args: symbol (str): Underlying index or stock ticker (e.g. 'NIFTY', 'BANKNIFTY'). api_key (str, optional): API Key. If omitted, uses OPTIONCONTEXT_API_KEY from environment. |
| get_historical_dataA | Fetch historical daily/intraday OHLCV candles (Requires Plan B subscription). Args: symbol (str): Ticker symbol. from_date (str): YYYY-MM-DD. to_date (str): YYYY-MM-DD. interval (str): Candle interval ('ONE_MINUTE', 'FIVE_MINUTE', 'FIFTEEN_MINUTE', 'ONE_DAY'). Default is 'ONE_DAY'. api_key (str, optional): API Key. |
| get_batch_market_contextA | Fetch live quote details, last traded price (LTP), volume, and context for a batch of Stocks, Indices, or Futures. Args: symbols (list[str]): Ticker symbols (e.g. ['NIFTY', 'RELIANCE']). expiry (str): Expiry cycle ('SPOT', 'NEAR', 'FAR', 'NEXT'). Default is 'SPOT'. api_key (str, optional): API Key. If omitted, uses OPTIONCONTEXT_API_KEY from environment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a clearly distinct purpose: market context for a single symbol, batch market context, option chain, historical data, symbol search, and API key info. The single versus batch distinction is clear, and option chain/historical data are fundamentally different data types.
All tools use lowercase snake_case, and five of six follow a consistent 'get_' prefix pattern. The exception is 'suggest_symbols', which still uses a verb but deviates from the 'get_' convention, making it slightly inconsistent.
Six tools is well within the ideal range for a market data server. Each tool covers a necessary function without unnecessary bloat, making the count appropriate for the server's stated purpose.
The tool surface covers the core needs of a market data context server: live quotes (single and batch), option chains, historical data, symbol resolution, and API key validation. No obvious dead ends or missing operations for the intended use case.