No user-submitted related servers found.
Scored across 8 tools
The get/search/list verbs give some separation, but four of eight tools (get_speech, get_speech_context, list_committees, list_meetings) ship with empty descriptions, forcing the agent to guess their boundary from the name alone. Worse, explore_issue explicitly performs bill, meeting, and speech discovery and warns against calling the discovery tools first, so its boundary with search_bills/search_speeches/list_meetings is defined only by prose the agent must parse mid-task.
Every name is snake_case verb_noun (get_speech, search_speeches, list_committees, get_bill_status, explore_issue), with no camelCase or bare nouns mixed in. The verb vocabulary (get/search/list/explore) is applied predictably: get for single retrieval, search for queries, list for enumerations.
Eight tools is a sensible size for a legislative research domain, and each named tool maps to a recognizable resource. However, explore_issue is a mega-tool that subsumes much of search_speeches, search_bills, list_meetings, and get_bill_status, so a few tools earn only a marginal claim on their own existence.
Speeches, context, committees, meetings, bills, and status are covered, but there is no way to fetch a specific meeting's detail/minutes or a committee's page directly, so list_enumeration tools dead-end. The descriptions repeatedly route the agent to a durable research workflow via start_research, yet no such tool exists in this set, leaving an advertised but unreachable path.