Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_house_votes

Retrieve detailed House vote data from the official Congress.gov API to analyze legislative decisions and track voting records by congress, session, and roll call number.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) session: Session number (1 or 2) roll_call_number: Specific roll call vote 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: House vote data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
sessionNo
roll_call_numberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The handler function for the 'get_house_votes' MCP tool. It is decorated with @mcp.tool() for registration and implements the logic to fetch House roll call vote data from the Congress.gov API using requests, handling parameters for filtering and pagination, with error handling for API requests.
    @mcp.tool()
    async def get_house_votes(
        congress: int | None = None,
        session: int | None = None,
        roll_call_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve House vote information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/HouseRollCallVoteEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            session: Session number (1 or 2)
            roll_call_number: Specific roll call vote 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: House vote data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/house-vote"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if session:
                url += f"/{session}"
                if roll_call_number:
                    url += f"/{roll_call_number}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for house votes
        }
    
        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 house vote information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While it mentions the API source and return format ('dict: House vote data'), it lacks critical behavioral information: whether this is a read-only operation, authentication requirements, rate limits, error handling, or pagination behavior beyond offset/limit parameters. The external documentation link doesn't compensate for missing behavioral details in the description itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably structured with clear sections (purpose, args, returns) but includes unnecessary elements. The external documentation link in the first sentence doesn't help an AI agent select/invoke the tool and could be omitted. The parameter explanations are helpful but make the description longer than necessary for optimal conciseness.

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 with 0% schema coverage and no output schema, the description provides good parameter documentation but lacks important contextual information. It doesn't explain the return structure beyond 'dict: House vote data,' doesn't mention error conditions or authentication needs, and provides no guidance on tool selection among siblings. For a data retrieval tool with many parameters, this leaves significant gaps in understanding how to effectively use it.

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?

With 0% schema description coverage (titles only, no descriptions), the description provides substantial parameter semantics beyond the schema. It explains each parameter's purpose, provides examples (e.g., '118 for 118th Congress'), format requirements ('YYYY-MM-DDTHH:MM:SSZ format'), and constraints ('max 250, default 20'). This significantly compensates for the schema's lack of descriptions, though it doesn't cover all possible edge cases.

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 tool's purpose: 'Retrieve House vote information from the Congress.gov API.' It specifies the resource (House vote information) and the source (Congress.gov API). However, it doesn't explicitly differentiate this from sibling tools like get_bills or get_members, which would be needed for a score of 5.

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 (e.g., get_bills, get_members, get_committees), there's no indication of when House vote retrieval is appropriate versus other congressional data tools. The link to external documentation doesn't substitute for explicit usage guidance.

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