Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. get_trades and get_top_movers lack descriptions for all parameters (ndays, symbol, date). get_todays_price description is misleading (mentions NASDAQ/NYSE/AMEX but tool is for NSEI/FMP data). No output schemas documented. Parameter descriptions are minimal (10-20 chars). No error handling guidance. Tool composition is reasonable but parameter naming could be more explicit (e.g., 'ticker' vs 'symbol' inconsistency across tools).

• Document output schemas for all three tools. Example for get_trades: 'Returns array of {symbol, date, open, high, low, close, volume}' with field types and descriptions.
• Expand parameter descriptions to 50-150 chars with constraints. E.g., 'ndays: Number of trading days to look back (1-365, default 1). Larger values return historical data; smaller values focus on recent trades.'
• Fix get_todays_price description to accurately reflect NSEI/FMP scope: 'Get the latest available price for a given stock ticker from the National Stock Exchange of India via Financial Modeling Prep API.'
• Standardize parameter naming: rename 'ticker' to 'symbol' in get_todays_price, or vice versa across all tools. Consistency enables LLM tool chaining without field mapping confusion.
• Add error handling guidance to each tool description. E.g., 'If symbol not found, returns empty array. If date is a weekend/holiday, returns data for the previous trading day.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry