Scored across 61 tools
The full/simple/keys variants are consistently documented, so most tools are clearly separated by payload depth and scope. However, the set is large enough that some boundaries are fuzzy—notably get_team_media vs get_team_social_media and get_team_history vs the various _all aggregates—so an agent must read descriptions carefully to avoid misselection.
Every tool follows the get_<resource>[_scope][_simple|_keys] convention, with uniform use of suffixes to indicate payload size and modifiers like _all, _by_year, and _event. The naming is highly predictable and consistent across all 61 tools.
61 tools is a very large surface for an agent to navigate, and most simple/keys variants could have been collapsed into optional result-shaping parameters. While the FRC domain is broad, this count falls well into the too-many range and will slow down tool discovery and selection.
The read-only FRC domain is covered extremely thoroughly: teams, events, matches, districts, awards, media, rankings, OPR, predictions, statuses, and even robot telemetry all have dedicated tools. There are no obvious dead ends for scouting, research, or live event analysis workflows.