Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Search Committees - Find congressional committees by chamber and type

search_committees

Find congressional committees by keyword, chamber, committee type, or Congress number. Get matching committees with basic information for legislative research.

Instructions

Search for / browse congressional committees.

Args:
    ctx: Context for API requests
    keywords: Optional keywords to search committee information. When omitted,
              lists committees (optionally filtered by chamber/type).
    chamber: Chamber ('House', 'Senate', or 'Joint')
    committee_type: Type of committee ('Standing', 'Select', etc.)
    congress: Optional Congress number (e.g., 119)
    limit: Maximum number of committees to return

Returns:
    List of matching committees with basic information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
chamberNo
congressNo
keywordsNo
committee_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when success is false: the section-9 error envelope
itemsNoResults of other kinds (bills, reports, communications, nominations), as returned by Congress.gov
contextYesContext about the search or operation performed
membersNoMember results
successYesWhether the operation was successful
summaryYesHuman-readable summary of the results
item_kindNoWhat `items` contains (bill, committee_report, communication, nomination, ...)
operationYesThe operation that was performed
committeesNoCommittee results
results_countYesNumber of items returned (equals the populated list's length)
Install Server

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description takes on the full behavioral burden. It clearly states the search-or-list behavior, optional filtering, limit semantics, and that it returns 'a list of matching committees with basic information.' It could disclose more about pagination or sorting, but the core behavior is transparent.

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

Conciseness4/5

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

The description is well structured with a front-loaded purpose sentence and a compact Args/Returns format. The only minor waste is the 'ctx: Context for API requests' line, which is not an actual schema parameter and adds little value for an MCP agent.

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

Completeness4/5

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

For a 5-parameter search tool with an output schema present, the description covers the main usage modes and return shape. It lacks detail on sort order or pagination behavior, but the existing coverage is enough for an agent to select and call the tool correctly in most cases.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does. Every parameter is meaningfully explained: keywords behavior, chamber examples, committee_type examples, congress example with 119, and limit as a maximum count. This substantially exceeds what the bare schema provides.

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

Purpose5/5

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

The description opens with a specific action and resource: 'Search for / browse congressional committees.' The title and parameter list further clarify that it finds committees by chamber and type, which cleanly separates it from sibling tools like search_bill_text and search_members.

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

Usage Guidelines3/5

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

The description gives useful behavior guidance such as 'When omitted, lists committees (optionally filtered by chamber/type),' which clarifies search vs browse usage. However, it does not explicitly mention when not to use this tool or name any alternative tools for different committee-related tasks.

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

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