What problem does it solve?
Prevents incorrect or ambiguous StockSearcher MCP calls by enforcing market, code, and date validation and by guiding the precise selection of the correct MCP tool so engineers avoid blocked calls, unsupported markets, and misinterpreted prediction data.
Core Features & Use Cases
- Deterministic tool selection: Choose list_stocks, stock_data, list_predict_dates, or predict_rows based on the exact data need.
- Strict parameter validation: Require supported market codes, validated stock codes, and YYYY-MM-DD formatted as_of dates before executing calls.
- Clear query framing and reporting: Mandate explicit statement of intent (discovery, history, prediction dates, or prediction rows), market, and row/date limits, and report which tool was used and why.
- Use Case: An engineer preparing prediction rows must confirm market and as_of, select predict_rows, validate date format, execute the call, and summarize results in plain language.
Quick Start
Ask the agent to validate the market and required parameters, select the appropriate StockSearcher MCP tool, execute the call, and explain the tool choice and result meaning.