Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_house_communication

Retrieve House communication data from Congress.gov, including executive communications, memorials, presidential messages, and petitions, with filtering by congress, type, number, and date range.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) communication_type: Type of communication - ec: Executive Communication - ml: Memorial - pm: Presidential Message - pt: Petition communication_number: Specific communication 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 communication data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
communication_typeNo
communication_numberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The primary handler function decorated with @mcp.tool(), implementing the logic to fetch House communication data from the Congress.gov API. Includes parameter definitions serving as input schema and detailed docstring documentation.
    @mcp.tool()
    async def get_house_communication(
        congress: int | None = None,
        communication_type: str | None = None,
        communication_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve House communication information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/HouseCommunicationEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            communication_type: Type of communication
                - ec: Executive Communication
                - ml: Memorial
                - pm: Presidential Message
                - pt: Petition
            communication_number: Specific communication 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 communication data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/house-communication"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if communication_type:
                url += f"/{communication_type}"
                if communication_number:
                    url += f"/{communication_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 house communication 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?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the API source and provides a documentation link, but doesn't describe authentication requirements, rate limits, error behavior, or what specific data fields are returned. 'Retrieve' implies a read operation, but there's no explicit safety declaration. The description adds minimal behavioral context beyond the basic operation.

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 effectively for parameter details. It's appropriately sized for a 7-parameter tool. The external documentation link is useful but doesn't disrupt the flow. Minor improvement could be front-loading more critical information 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 retrieval tool with no annotations and no output schema, the description provides good parameter documentation but lacks important context. It doesn't explain the return data structure, pagination behavior (beyond offset/limit parameters), error conditions, or authentication requirements. The external documentation link helps but doesn't make the description itself complete for agent usage.

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, the description provides excellent parameter documentation that fully compensates. It explains all 7 parameters with clear examples (e.g., '118 for 118th Congress'), enumerated values for communication_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 'Retrieve House communication information from the Congress.gov API' which specifies both the action (retrieve) and resource (House communication information). It distinguishes from siblings like 'get_senate_communication' by specifying 'House' communication. However, it doesn't explicitly differentiate from other data retrieval tools like 'get_bills' or 'get_committees' beyond the resource type.

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 sibling tools like 'get_senate_communication' and 'get_bills' available, there's no indication of when House communications specifically are needed versus other legislative data sources. The external documentation link is helpful but doesn't provide in-description usage context.

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