Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_amendments

Retrieve U.S. Congressional amendment data from Congress.gov by specifying congress, amendment type, number, or date range to access legislative changes.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) amendment_type: Type of amendment - hamdt: House Amendment - samdt: Senate Amendment - suamdt: Senate Unprinted Amendment amendment_number: Specific amendment number (requires congress and amendment_type) 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: Amendment data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
amendment_typeNo
amendment_numberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The handler function for the 'get_amendments' MCP tool, decorated with @mcp.tool() for automatic registration with FastMCP. It constructs a URL and parameters for the Congress.gov amendments API endpoint and fetches the data using requests, handling errors gracefully.
    @mcp.tool()
    async def get_amendments(
        congress: int | None = None,
        amendment_type: str | None = None,
        amendment_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve amendments from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/AmendmentEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            amendment_type: Type of amendment
                - hamdt: House Amendment
                - samdt: Senate Amendment
                - suamdt: Senate Unprinted Amendment
            amendment_number: Specific amendment number (requires congress and amendment_type)
            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: Amendment data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/amendment"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if amendment_type:
                url += f"/{amendment_type}"
                if amendment_number:
                    url += f"/{amendment_number}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for amendments
        }
    
        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 amendments: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:99-99 (registration)
    The @mcp.tool() decorator registers the get_amendments function as an MCP tool.
    @mcp.tool()
  • Input schema defined by function parameters with type hints and detailed docstring describing arguments and return type.
    async def get_amendments(
        congress: int | None = None,
        amendment_type: str | None = None,
        amendment_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve amendments from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/AmendmentEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            amendment_type: Type of amendment
                - hamdt: House Amendment
                - samdt: Senate Amendment
                - suamdt: Senate Unprinted Amendment
            amendment_number: Specific amendment number (requires congress and amendment_type)
            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: Amendment data from Congress.gov API
        """
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the API endpoint documentation link and return format ('dict: Amendment data'), but lacks critical behavioral details like rate limits, authentication requirements, error handling, pagination behavior beyond offset/limit, or what happens when parameters are omitted.

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 details. While the external documentation link adds some length, every sentence provides value. It could be slightly more front-loaded with a clearer summary before the parameter details.

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 does a good job with parameter documentation but has significant gaps. It lacks behavioral context (rate limits, auth), doesn't explain the return structure beyond 'dict', and provides no sibling differentiation. The parameter documentation compensates somewhat, but overall completeness is only adequate.

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 beyond the bare schema. It explains each parameter's purpose, provides examples (e.g., '118 for 118th Congress'), enumerates amendment_type values with descriptions, clarifies dependencies ('requires congress and amendment_type'), and specifies format requirements ('YYYY-MM-DDTHH:MM:SSZ format').

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 resource ('amendments from the Congress.gov API'), making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'get_bills' or 'get_members', but the specific resource focus provides implicit differentiation.

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_bills' or other legislative data tools. It mentions parameter dependencies ('requires congress and amendment_type') but offers no contextual usage advice for the agent.

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