Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_hearings

Retrieve congressional hearing data from the Congress.gov API by specifying congress, chamber, date range, and other parameters to access official legislative proceedings.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) chamber: Chamber (house, senate) hearing_number: Specific hearing number 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: Hearing data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
chamberNo
hearing_numberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The handler function for the 'get_hearings' MCP tool. Decorated with @mcp.tool() for automatic registration. Fetches hearing data from the Congress.gov API using provided parameters, handles pagination and date filtering, and returns JSON response or error.
    @mcp.tool()
    async def get_hearings(
        congress: int | None = None,
        chamber: str | None = None,
        hearing_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve hearing information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/HearingEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            chamber: Chamber (house, senate)
            hearing_number: Specific hearing number
            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: Hearing data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/hearing"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if chamber:
                url += f"/{chamber}"
                if hearing_number:
                    url += f"/{hearing_number}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for hearings
        }
    
        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 hearing information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:613-613 (registration)
    The @mcp.tool() decorator registers the get_hearings function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the API endpoint and provides parameter details, it doesn't describe important behavioral aspects like rate limits, authentication requirements, error handling, pagination behavior (beyond offset/limit parameters), or what happens when parameters are omitted. For a 7-parameter tool with zero annotation coverage, this is insufficient.

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, documentation link, args, returns) and uses bullet points effectively. While it could be slightly more concise by integrating some parameter details, every sentence serves a purpose and the information is front-loaded with the core functionality 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?

For a 7-parameter tool with no annotations and no output schema, the description provides good parameter documentation but lacks behavioral context. The return value description ('Hearing data from Congress.gov API') is vague without an output schema. Given the complexity and absence of structured metadata, the description should do more to explain behavior, error cases, and result format.

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?

With 0% schema description coverage, the description fully compensates by providing clear documentation for all 7 parameters. Each parameter gets specific details: congress includes an example (118), chamber lists valid values (house, senate), hearing_number is explained, offset and limit have defaults, and datetime parameters specify exact format requirements. This adds substantial value beyond the bare schema.

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 clearly states the specific action ('Retrieve hearing information') and resource ('from the Congress.gov API'), distinguishing it from sibling tools like get_bills or get_committees. It provides a precise verb+resource combination that leaves no ambiguity about what this tool does.

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 like get_committee_meetings or other sibling tools. While it mentions the API endpoint documentation, it doesn't offer any contextual advice about appropriate use cases, prerequisites, or comparisons with related tools.

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