ledgerfc

Most tools target clearly distinct resources or actions, but get_predictions and get_value_bets overlap conceptually as both return upcoming predictions with model-vs-market edge, differing mainly by PRO status and positive edge filtering. The CLV-related tools (get_contributor_score, get_leaderboard, get_track_record) are also related, though each has a distinct purpose.

The naming pattern is mostly consistent with a get_<resource> convention across the majority of tools. Minor deviations include fetch and search as verbs instead of get_, and the abbreviated get_arbs instead of a more consistent get_arbitrage_opportunities.

With 13 tools, the server is well-scoped for a prediction/betting platform. Each tool serves a clear function in the workflow: discovering predictions, placing bets, viewing bets/balance, submitting predictions, and checking CLV/leaderboard data. The count feels complete without bloating the surface.

The domain is well covered: search/fetch predictions, view upcoming picks, place paper bets, track bets and balance, submit predictions, and review CLV/leaderboard stats. Minor gaps exist such as no cancel/void bet operation or more granular market data, but agents can execute the core workflow without dead ends.