Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_congressional_record

Retrieve official congressional record data from Congress.gov to access legislative proceedings, debates, and floor actions by volume, page, or date range.

Instructions

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

Args: volume: Volume number page_prefix: Page prefix - h: House section - s: Senate section - e: Extensions of Remarks section - d: Daily Digest section page_number: Specific page 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: Congressional record data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
volumeNo
page_prefixNo
page_numberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The core handler function implementing the get_congressional_record tool. It constructs the API URL based on provided parameters (volume, page_prefix, page_number), adds pagination and date filters, calls the Congress.gov API using requests, and handles errors by returning an error dict.
    @mcp.tool()
    async def get_congressional_record(
        volume: int | None = None,
        page_prefix: str | None = None,
        page_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve congressional record information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/DailyCongressionalRecordEndpoint.md
    
        Args:
            volume: Volume number
            page_prefix: Page prefix
                - h: House section
                - s: Senate section
                - e: Extensions of Remarks section
                - d: Daily Digest section
            page_number: Specific page 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: Congressional record data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/congressional-record"
    
        url = base_url
        if volume:
            url += f"/{volume}"
            if page_prefix:
                url += f"/{page_prefix}"
                if page_number:
                    url += f"/{page_number}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)
        }
    
        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 congressional record information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:672-672 (registration)
    The @mcp.tool() decorator registers the get_congressional_record function as an MCP tool with FastMCP instance.
    @mcp.tool()
  • The function signature and docstring define the input schema (parameters with types and descriptions) and output type (dict) for the tool.
    async def get_congressional_record(
        volume: int | None = None,
        page_prefix: str | None = None,
        page_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
Behavior3/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 source and provides some parameter details (like limit max of 250), but doesn't cover important aspects like rate limits, authentication requirements, error handling, or what specific data fields are returned in the 'congressional record data'.

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 parameter explanations. It's appropriately sized for a 7-parameter tool, though the documentation link could be more integrated rather than standalone.

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 7 parameters, 0% schema coverage, no annotations, and no output schema, the description does a good job with parameters but leaves gaps in behavioral context. It explains what the tool does and documents parameters well, but doesn't provide enough information about the return structure, error conditions, or how this differs from sibling tools.

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 and 7 parameters, the description provides excellent parameter semantics compensation. It explains each parameter clearly, including the meaning of page_prefix values (h, s, e, d), default values for offset and limit, format requirements for timestamps, and the maximum limit constraint.

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 verb 'retrieve' and the resource 'congressional record information from the Congress.gov API', making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_daily_congressional_record' or 'get_bound_congressional_record', which appear to be related alternatives.

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_daily_congressional_record' or 'get_bound_congressional_record'. It mentions a documentation link but doesn't explain the specific use case or context for this particular endpoint compared to siblings.

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