Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_summaries

Retrieve bill summaries from Congress.gov to understand legislative activity. Filter by congress, bill type, date range, and sorting options for targeted research.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) bill_type: Type of bill - hr: House of Representatives Bill - s: Senate Bill - hjres: House Joint Resolution - sjres: Senate Joint Resolution - hconres: House Concurrent Resolution - sconres: Senate Concurrent Resolution - hres: House Simple Resolution - sres: Senate Simple Resolution 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) sort: Sort order ('updateDate+asc' or 'updateDate+desc')

Returns: dict: Summary data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
bill_typeNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo
sortNoupdateDate+desc

Implementation Reference

  • The handler function for the 'get_summaries' MCP tool. It is decorated with @mcp.tool(), which also serves as the registration. The function signature and docstring define the input schema. It makes an API request to Congress.gov /v3/summaries endpoint with constructed URL and parameters, handling errors.
    @mcp.tool()
    async def get_summaries(
        congress: int | None = None,
        bill_type: str | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None,
        sort: str = "updateDate+desc"
    ) -> dict:
        """
        Retrieve bill summaries from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/SummariesEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            bill_type: Type of bill
                - hr: House of Representatives Bill
                - s: Senate Bill
                - hjres: House Joint Resolution
                - sjres: Senate Joint Resolution
                - hconres: House Concurrent Resolution
                - sconres: Senate Concurrent Resolution
                - hres: House Simple Resolution
                - sres: Senate Simple Resolution
            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)
            sort: Sort order ('updateDate+asc' or 'updateDate+desc')
    
        Returns:
            dict: Summary data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/summaries"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if bill_type:
                url += f"/{bill_type}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250),  # API max limit for summaries
            "sort": sort
        }
    
        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 summaries: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:161-161 (registration)
    The @mcp.tool() decorator registers the get_summaries function as an MCP tool.
    @mcp.tool()
  • The docstring provides detailed input schema and description for the tool, used by FastMCP for tool schema generation.
    """
    Retrieve bill summaries from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/SummariesEndpoint.md
    
    Args:
        congress: Congress number (e.g., 118 for 118th Congress)
        bill_type: Type of bill
            - hr: House of Representatives Bill
            - s: Senate Bill
            - hjres: House Joint Resolution
            - sjres: Senate Joint Resolution
            - hconres: House Concurrent Resolution
            - sconres: Senate Concurrent Resolution
            - hres: House Simple Resolution
            - sres: Senate Simple Resolution
        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)
        sort: Sort order ('updateDate+asc' or 'updateDate+desc')
    
    Returns:
        dict: Summary data from Congress.gov API
    """
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 endpoint and provides parameter details, but doesn't describe important behavioral aspects like rate limits, authentication requirements, error conditions, or pagination behavior beyond the offset/limit parameters. The description doesn't contradict any annotations (since none exist), but leaves significant behavioral questions unanswered.

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 (Args, Returns) and uses bullet points for the bill_type parameter. It's appropriately sized for a 7-parameter tool. However, the first sentence could be more front-loaded with key information, and the external documentation link could be better integrated rather than appearing as the second sentence.

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 important contextual information. It doesn't explain what 'summary data' contains, how results are structured, or provide examples of return values. The external documentation link helps, but the description itself should provide more complete guidance for agent usage given the tool's complexity.

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?

Given 0% schema description coverage, the description provides excellent parameter semantics that fully compensate. It explains all 7 parameters with clear explanations, examples (e.g., '118 for 118th Congress'), enumerated values for bill_type, format specifications (YYYY-MM-DDTHH:MM:SSZ), and default values. This adds substantial meaning beyond what the bare schema provides.

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') and resource ('bill summaries from the Congress.gov API'), making the purpose immediately understandable. It distinguishes itself from siblings by focusing specifically on summaries rather than bills, amendments, or other legislative documents. However, it doesn't explicitly contrast with similar tools like 'get_bills' in terms of what summaries contain versus full bill text.

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. With many sibling tools available (like get_bills, get_amendments, get_committee_reports), there's no indication of when summaries are appropriate versus full documents or other legislative data. The only contextual guidance is the link to external documentation, which doesn't help the agent make tool selection decisions.

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