Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_committees

Retrieve committee data from the U.S. Congress.gov API to access legislative committee information, including membership, activities, and historical records.

Instructions

Retrieve committee information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/CommitteeEndpoint.md

Args: system_code: Specific committee system code (e.g., "hsag" for House Agriculture) offset: Starting record (default 0) limit: Maximum records to return (max 250, default 20) from_datetime: Start timestamp (YYYY-MM-DDTHH:MM:SSZ format) to_datetime: End timestamp (YYYY-MM-DDTHH:MM:SSZ format)

Returns: dict: Committee data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_codeNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The main handler function for the 'get_committees' MCP tool. Decorated with @mcp.tool() which registers it with the MCP server. Fetches committee data from the Congress.gov API based on provided parameters.
    @mcp.tool()
    async def get_committees(
        system_code: str | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve committee information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/CommitteeEndpoint.md
    
        Args:
            system_code: Specific committee system code (e.g., "hsag" for House Agriculture)
            offset: Starting record (default 0)
            limit: Maximum records to return (max 250, default 20)
            from_datetime: Start timestamp (YYYY-MM-DDTHH:MM:SSZ format)
            to_datetime: End timestamp (YYYY-MM-DDTHH:MM:SSZ format)
    
        Returns:
            dict: Committee data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/committee"
    
        url = base_url
        if system_code:
            url += f"/{system_code}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for committees
        }
    
        if from_datetime:
            params["fromDateTime"] = from_datetime
        if to_datetime:
            params["toDateTime"] = to_datetime
    
        try:
            response = requests.get(url, params=params)
            response.raise_for_status()
            return response.json()
    
        except requests.exceptions.RequestException as e:
            return {
                "error": f"Failed to retrieve committee information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions retrieving data and includes a link to external documentation, but doesn't describe key behaviors like whether this is a read-only operation, error handling, rate limits, authentication needs, or response structure. The link adds some context but doesn't compensate for missing behavioral details in the description itself.

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 clear sections (purpose, args, returns) and uses bullet points for parameters. It's appropriately sized, though the external link might be considered extraneous. Every sentence adds value, and the information is front-loaded with the core purpose stated first.

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?

Given the tool's moderate complexity (5 parameters, no annotations, no output schema), the description is partially complete. It covers parameters well but lacks behavioral context, usage guidelines, and output details. The external link provides a fallback, but the description itself doesn't fully address the tool's operational needs, especially for an API call with multiple parameters.

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?

The description adds substantial meaning beyond the input schema, which has 0% description coverage. It explains each parameter's purpose with examples (e.g., 'hsag' for House Agriculture), default values, formats (YYYY-MM-DDTHH:MM:SSZ), and constraints (max 250 for limit). This effectively compensates for the schema's lack of documentation, though it could benefit from more context on parameter interactions.

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

Purpose4/5

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

The description clearly states the tool's purpose as 'Retrieve committee information from the Congress.gov API,' which includes a specific verb ('Retrieve') and resource ('committee information'). It distinguishes from siblings by focusing on committees rather than bills, members, votes, etc., though it doesn't explicitly contrast with similar tools like 'get_committee_meetings' or 'get_committee_reports.'

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions a link to full documentation but doesn't specify use cases, prerequisites, or exclusions. With sibling tools like 'get_committee_meetings' and 'get_committee_reports' available, this lack of differentiation is a significant gap.

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/AshwinSundar/congress_gov_mcp'

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