No user-submitted related servers found.
Scored across 5 tools
Each tool targets a distinct resource: metadata, state list, single state record, CE rules, and full-text search. The only mild overlap is between get_state ("full requirement record") and get_state_ce (continuing-education rules), since CE content may be perceived as part of the full record, but the descriptions make the boundary clear enough.
All names follow a clean verb_noun snake_case pattern (get_/list_/search_) with the resource appended, and the get_state / get_state_ce suffixing is predictable and readable. No mixing of conventions.
Five tools map one-to-one onto the underlying read-only API surface (meta, states list, state detail, CE detail, search), with no filler or redundant wrappers. Well-scoped for a focused reference-data server.
The read-only domain is essentially covered: version metadata, enumeration, per-state detail, CE detail, and search, with no write operations expected for a curated data API. Minor gaps remain, such as no multi-state comparison or bulk/aggregate query beyond search, but agents can compose existing tools to work around this.