Scored across 41 tools
Most tools have clearly distinct purposes (quotes vs. order placement vs. data research are separated well). However, the set includes many overlapping data tools: get_market_context, get_news, get_candles, get_crypto_movers, pm_data_events, pm_data_event, pm_data_disagreements, pm_data_overview, discover_pm_markets — an agent can struggle to pick which PM research tool answers a given question, and get_market_context vs. get_candles vs. get_crypto_movers overlap conceptually.
There are several prefix conventions (pm_data_*, get_*, pm_/futures_/spot_ prefixes) and the domain prefixes are mostly consistent within families (pm_data_event / pm_data_events, spot_quote / place_spot_order), but mixing 'get_' verbs with domain-prefixed action verbs (open_pm_position, place_spot_order, export_run_evidence, report_pm_opportunity) yields a mixed but still readable scheme.
41 tools is very heavy for a single agent trading surface, and several are near-duplicates (pm_data_event / pm_data_events, export_agent_ledger / export_run_evidence / get_agent_ledger). The public PM data tools are a distinct product surface bolted onto the trading server, inflating the count well past what an agent can reliably navigate.
The domain (paper trading across spot, futures, PM plus performance/audit) is covered end-to-end: quotes, open/close, SL/TP, order management, portfolio, trades, leaderboard, ledger. Minor gaps exist — no explicit cancel for futures/PM positions beyond close, no direct 'modify order' for spot, and resolution of PM markets is only read-only — but core workflows are present.