No user-submitted related servers found.
Scored across 210 tools
There is heavy functional overlap across the 210 tools: get_member_voting, get_commons_voting_record_for_member, get_lords_voting_record_for_member, check_mp_vote, and search_commons_divisions all retrieve voting records; get_departments and get_answering_bodies appear to do the same thing; get_sitting_dates vs get_hansard_calendar vs search_calendar; get_constituency_latest_election vs get_constituency_election_result vs get_election_results_for_constituency. Agents will struggle to choose the right tool, especially between the many 'summary' aggregators and their base components.
Mostly snake_case with verb_noun prefixes (get_, search_, list_, browse_), but there are significant deviations: 'happening_now_in_commons', 'order_order', 'parties_list_by_house' (noun_verb), 'bill_types'/'bill_stages' (bare nouns), 'interests_categories'. The mix of get_/search_/list_/browse_/bare-noun is readable but not predictable.
210 tools is an extreme mismatch for even a large domain like UK Parliament. The surface includes redundant peers (get_member_portrait_url vs get_member_thumbnail_url, many RSS variants, many 'by_id' lookups), which forces the agent to navigate an enormous catalog. This clearly exceeds any reasonable MCP tool count.
Coverage is remarkably comprehensive: members, bills, committees, Hansard, divisions, interests, EDMs, SIs, treaties, Erskine May procedure, calendar, written questions/statements. CRUD-style read coverage of the parliamentary domain is near-total, though there are notable redundancies rather than true gaps, and the server is purely read-only (which fits the public data domain).