Quantplay

Most tools target distinct resources: accounts, orders, positions, holdings, margins, option chains, historical data, strategies, and connections. The main ambiguity is the P&L/analytics cluster (get_account_stats, get_pnl_history, get_live_pnl, get_pnl_stats, get_pnl_stats_index), where descriptions clarify boundaries but selection still requires care. get_connections versus get_sync_connections is also close, though the descriptions explicitly separate listing from drift comparison.

Every tool uses the same get_ + snake_case noun pattern, with no mixed casing or verb styles. The names are predictable and readable throughout the set. The only limitation is that the entire surface is read-oriented, but naming itself is highly consistent.

Eighteen tools is on the heavy side but justified by the broad trading/analytics domain, covering accounts, orders, positions, holdings, margins, options, P&L, strategies, and copy-trading connections. Each tool appears to earn its place by exposing a distinct data view rather than duplicating another. It is slightly over the ideal 3-15 range but still reasonable.

The surface is almost entirely read-only and omits core trading actions that the descriptions explicitly reference, including place_order, update_risk_management, and update_connection. An agent can inspect accounts, positions, orders, and analytics but cannot place, modify, or cancel orders, manage risk settings, or configure copy-trading connections. These are significant gaps for a trading platform and will cause agent task failures.