No user-submitted related servers found.
Scored across 8 tools
The tools mostly target distinct resources (bill, history, hearings, member, committee, votes, recent legislation, search), but get_bill_history and get_votes both cover vote/roll-call information and their boundary is muddied by references to absent tools like vote_breakdown and 'local get_bill_history.' Inputs sometimes distinguish them (file number vs EventItemId), but the repeated local/live framing confuses a set that contains only live tools.
All names use predictable snake_case with a leading verb: get_, list_, search_. Minor compound forms like get_bill_history and search_legislation_live are still readable and consistent with the pattern.
Eight tools is well within the appropriate range for a read-only legislative lookup server. Each tool maps to a distinct resource or action, so the count itself is well-scoped.
The descriptions repeatedly direct agents to search_bills, vote_breakdown, and a local index that are not in this server, creating significant dead ends. In particular, get_votes requires an EventItemId, but the only in-set source is upcoming hearing agenda items; the description explicitly says live get_bill_history returns an event ID rather than an event item ID, leaving no reliable path to past roll-call votes.