This server has 12 tools with reasonable naming conventions and basic descriptions, but suffers from significant gaps in schema completeness, parameter documentation, and error handling. Most tools have empty input schemas (no parameters documented), making them difficult for LLMs to compose and validate input. Descriptions exist but are often generic and lack dependency hints or recovery guidance. The server exposes financial trading operations (place_order, cancel_order) without adequate confirmation or dry-run patterns, creating safety risks. No output schemas are documented, and error handling is minimal.

• Document output schemas for all 12 tools in the Tool definitions. Include field names, types, and descriptions. Example for get_holdings: {type: 'object', properties: {holdings: {type: 'array', items: {type: 'object', properties: {isin: {type: 'string'}, quantity: {type: 'integer'}, avg_price: {type: 'number'}, ...}}}}}
• Add a 'dry_run' boolean parameter to place_order, and require a confirmation step before execution. Return a preview showing quantity, price, total cost, and impact on margin. Only execute on a second explicit confirmation call.
• Wrap place_order, modify_order, and cancel_order execution in explicit permission checks. Log every call with timestamp, order details, outcome, and user identity. Route logs to a dedicated audit stream for compliance.
• Convert order_type in place_order to an enum: ['MARKET', 'LIMIT', 'SL', 'SL-M']. Add min/max price constraints, hint on when price/trigger_price are required. Example: 'price (number, required for LIMIT/SL orders, min 0.01, max 1000000)'.
• Add error recovery guidance to all tools. Example for place_order: 'If rejected due to insufficient margin, call get_margins() to check available funds. If rate limited, retry after 60 seconds.'
• Implement pagination on get_holdings, get_positions, get_orders, get_instruments. Add optional limit (default 20, max 100) and offset or cursor parameters. Return total_count and next_offset in response.
• Document fallback behavior in get_quote and get_ohlc descriptions. State explicitly: 'If market data is unavailable, this tool returns data from your holdings/positions instead. For real-time quotes, prefer this tool first.'

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

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