Skip to main content
Glama
amurshak

CongressMCP-full

Search Committees - Find congressional committees by chamber and type

search_committees

Retrieve U.S. congressional committees from Congress.gov. Filter by chamber and committee type to find House, Senate, or Joint legislative panels.

Instructions

Search for congressional committees.

Args:
    ctx: Context for API requests
    chamber: Chamber ('House', 'Senate', or 'Joint')
    committee_type: Type of committee ('Standing', 'Select', etc.)
    limit: Maximum number of committees to return

Returns:
    List of matching committees with basic information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chamberNo
committee_typeNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the operation was successful
operationYesThe operation that was performed
results_countYesNumber of results returned
membersNoMember results
committeesNoCommittee results
summaryYesHuman-readable summary of the results
contextYesContext about the search or operation performed
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, leaving full burden on description. Mentions 'List of matching committees with basic information' but fails to clarify pagination behavior, default sorting, what 'basic information' includes, or error handling when no matches exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Uses structured Args/Returns format which is readable, but opens with redundant 'Search for congressional committees' that restates the tool name. The Returns section is somewhat superfluous given the output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Acceptable for a search tool with output schema present (reducing need for detailed return documentation). Compensates for zero schema coverage via Args section, but gaps remain in behavioral details and sibling differentiation necessary for a tool with 15+ siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the Args section provides essential value: documents chamber values ('House', 'Senate', 'Joint'), committee_type examples ('Standing', 'Select'), and limit purpose. However, 'etc.' for committee_type leaves values incomplete, and no format constraints are specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the core action ('Search for congressional committees') but lacks specificity regarding what distinguishes this from sibling tools like committee_intelligence or get_committee_bills. The Args section implies search by chamber/type, but the opening statement is vague and tautological with the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus alternatives (e.g., get_committee_bills for legislative activity vs. this for organizational listing). No mention of prerequisites or filtering strategies when all parameters are optional.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amurshak/congressMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server