Scored across 4 tools
Each tool has a clearly distinct purpose: get_stats (metadata survey), search_problems (keyword lookup), get_problem (fetch by id), and sample_problems (random draw). Descriptions explicitly cross-reference each other, telling the agent when to prefer search over sample and vice versa. There is no meaningful overlap that could cause misselection.
All four tools follow a uniform arquimedes_verb_noun pattern (get_stats, search_problems, get_problem, sample_problems) in consistent snake_case. Verb choice maps cleanly to action, and the server prefix is applied uniformly. No convention mixing.
Four tools is compact but each earns its place in a read-only database workflow: discover facets, search, retrieve, and sample. Nothing feels redundant or padded. The scope (browsing a problem corpus) is fully served without bloat.
The surface covers the core read lifecycle: facet discovery via stats, keyword search with filters, id-based full retrieval including solutions/hints, and random sampling. Minor gaps exist (e.g., no bulk multi-id fetch or explicit pagination controls), but these are workarounds an agent can handle. No single-purpose dead ends.