Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_senate_communication

Retrieve Senate communication data from Congress.gov, including executive communications, presidential messages, and petitions, filtered by congress, type, number, or date range.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) communication_type: Type of communication - ec: Executive Communication - pm: Presidential Message - pom: Petition or Memorial 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: Senate 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 handler function for the 'get_senate_communication' MCP tool. It queries the Congress.gov API for senate communications based on parameters like congress, communication_type, etc., handles pagination and date ranges, and returns the JSON response or error.
    @mcp.tool()
    async def get_senate_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 Senate communication information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/SenateCommunicationEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            communication_type: Type of communication
                - ec: Executive Communication
                - pm: Presidential Message
                - pom: Petition or Memorial
            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: Senate communication data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/senate-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 senate communication information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:967-967 (registration)
    The @mcp.tool() decorator registers the get_senate_communication function as an MCP tool.
    @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_senate_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:
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It mentions the API endpoint documentation link and basic return format ('dict: Senate communication data'), but doesn't disclose important traits like whether this is a read-only operation, rate limits, authentication requirements, error handling, or what specific data fields are returned. The description is functional but lacks operational transparency.

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 somewhat lengthy due to 7 parameters, every sentence adds value - the API documentation link is useful, parameter explanations are necessary given poor schema coverage, and the return statement is minimal but adequate.

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 is moderately complete. It thoroughly documents parameters but lacks behavioral context (rate limits, auth, error handling) and only vaguely describes returns ('dict: Senate communication data'). Given the complexity and absence of structured metadata, more operational details would improve completeness.

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 for 7 parameters, the description compensates well by providing clear explanations for all parameters, including examples (e.g., '118 for 118th Congress'), enumerated values for communication_type, format specifications ('YYYY-MM-DDTHH:MM:SSZ format'), 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 verb 'Retrieve' and resource 'Senate communication information from the Congress.gov API', making the purpose explicit. It distinguishes this tool from siblings like 'get_house_communication' by specifying Senate communications, but doesn't explain how it differs from other data retrieval tools in the same API family 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. While it's clearly for Senate communications (versus House communications), there's no mention of when to use this versus other congressional data tools like get_bills or get_committee_reports, nor any context about typical use cases or prerequisites for Senate communication data.

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