Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_committee_meetings

Retrieve committee meeting details from Congress.gov by specifying congress, chamber, date range, and pagination parameters to access legislative activity information.

Instructions

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
chamberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The core handler function decorated with @mcp.tool() that implements the get_committee_meetings tool. It fetches committee meeting data from the Congress.gov API v3/committee-meeting endpoint using requests, handles parameters like congress, chamber, pagination, and date ranges, and returns the JSON response or an error dict.
    @mcp.tool()
    async def get_committee_meetings(
        congress: int | None = None,
        chamber: str | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve committee meeting information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/CommitteeMeetingEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            chamber: Chamber (house, senate)
            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 meeting data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/committee-meeting"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if chamber:
                url += f"/{chamber}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for committee meetings
        }
    
        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 meeting information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:558-558 (registration)
    The @mcp.tool() decorator registers the get_committee_meetings function as an MCP tool.
    @mcp.tool()
  • The function signature defines the input schema (parameters with types and defaults) and output type (dict) for the tool.
    async def get_committee_meetings(
        congress: int | None = None,
        chamber: str | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
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. It mentions the API endpoint and return format ('dict: Committee meeting data'), but lacks critical behavioral details: whether this is a read-only operation, rate limits, authentication requirements, error handling, pagination behavior beyond offset/limit, or what specific data fields are included. The external documentation link is helpful but doesn't replace direct disclosure in the description.

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 effectively. Every sentence adds value: the first states the purpose, the second provides documentation reference, and the parameter explanations are essential. While slightly verbose due to detailed param documentation, this is justified given the 0% schema coverage. It could be more front-loaded by moving the returns statement earlier.

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 6 parameters with 0% schema coverage and no output schema, the description does a good job documenting parameters but has significant gaps. It lacks behavioral context (no annotations), doesn't explain the return structure beyond 'dict', and provides no usage guidance. For a data retrieval tool with multiple filtering parameters, the description is minimally adequate but leaves the agent to guess about important aspects like error cases, data format, and practical constraints.

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 provides excellent parameter documentation with clear explanations, examples, and constraints for all 6 parameters, despite 0% schema description coverage. It adds substantial value beyond the bare schema by explaining what each parameter means (e.g., 'Congress number (e.g., 118 for 118th Congress)'), format requirements ('YYYY-MM-DDTHH:MM:SSZ format'), and practical constraints ('max 250, default 20'). This fully compensates for the schema's lack of descriptions.

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 action ('Retrieve committee meeting information') and resource ('from the Congress.gov API'), providing a specific verb+resource combination. It distinguishes itself from siblings like 'get_committees' by focusing on meetings rather than committee entities. However, it doesn't explicitly differentiate from other meeting-related tools that might exist in the broader context.

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. While it mentions the API endpoint documentation, it doesn't specify use cases, prerequisites, or comparisons with sibling tools like 'get_hearings' or 'get_committees'. The agent must infer usage from the tool name and parameter set alone.

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