Scored across 25 tools
Most tools target clearly distinct resources or actions, and descriptions explicitly differentiate overlapping pairs like audio lanes, route tools, and trust tools. However, several closely related tools (e.g., steward_audio_match vs audio_rest/focus, steward_cheapest_route vs route_fees) still require careful reading to avoid misselection.
Names consistently use snake_case with domain prefixes (steward_ or trust_), which is predictable. The main deviation is that they do not follow a uniform verb_noun pattern, and the steward_/trust_ prefix split is a minor inconsistency.
25 tools is at the heavy end of the range, and the server bundles many unrelated utility services (weather, ISS, audio, jokes, crypto routes, trust) under one MCP. Each tool covers a distinct service, but the overall count feels borderline heavy for the apparent scope.
The surface covers the main domains: catalog/purchase flow, trust verification, payment receipts, and a broad set of utility APIs. Minor gaps exist (e.g., no explicit post-payment download tool and limited audio discovery beyond mood match), but agents can work around them.
