The server presents 23 tools with generally clear names and structured schemas. Most tools have descriptions and reasonable parameter definitions. However, there are notable gaps: several descriptions are terse (under 50 chars), many parameters lack detailed constraints, output schemas are not formally documented, and error handling guidance is minimal. The tools are well-organized into logical domains (trading, portfolio, forecasting, analysis), but lack the maturity expected of production-grade tools. Naming is verb-forward and consistent (get_*, place_*, calculate_*), which is positive. Parameters mostly have types and brief descriptions, but lack context about ranges, dependencies, and error conditions. This is a solid community effort but falls short of enterprise standards.

• Add formal output schema documentation for every tool. For get_markets, document the structure of returned market objects (ticker, yes_bid, yes_ask, no_bid, no_ask, etc.) with field types and descriptions.
• Expand descriptions to 80-150 characters. E.g., change 'Get list of markets' to 'Get open markets filtered by series, status, and limit. Use to discover trading opportunities and check liquidity before placing orders.'
• Convert inline enum values (city_code: 'NYC, CHI, MIA...') to proper JSON Schema enums: {"type": "string", "enum": ["NYC", "CHI", "MIA", ...]}.
• Add min/max bounds to numeric parameters. E.g., yes_price: {type: integer, minimum: 1, maximum: 99, description: 'Price in cents (1-99)...'}.
• Document place_order as a COMMAND tool with explicit warning about reversibility. Add guidance: 'This tool places a real order and charges fees. Consider calling calculate_edge first to validate the trade logic. Cancellation via cancel_order is possible but incurs slippage.'
• Add error recovery hints to place_order, cancel_order, and forecast tools. E.g., 'If balance insufficient, call get_balance first. If ticker invalid, call get_markets to verify.'
• For tools with optional parameters (series_ticker, status, category), clarify defaults and fallback behavior in descriptions.
• Add a per-tool note on idempotency. E.g., cancel_order should document: 'Idempotent, canceling an already-canceled order returns an error; use get_order to verify status before retrying.'
• Document tool chains explicitly. Add to parse_ticker: 'Call this first when analyzing a Kalshi ticker. Output fields (city, date, threshold) feed into calculate_edge and other analysis tools.'

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

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