Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_committee_prints

Retrieve committee print documents from Congress.gov to access legislative research materials from House, Senate, or joint committees.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) print_type: Type of print - hprt: House Print - sprt: Senate Print - jprt: Joint Committee Print print_number: Specific print 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: Committee print data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
print_typeNo
print_numberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The main handler function for the 'get_committee_prints' tool. Decorated with @mcp.tool() for automatic registration in FastMCP. Includes parameter type hints and comprehensive docstring defining the input schema. Fetches committee print data from the Congress.gov API based on provided filters.
    @mcp.tool()
    async def get_committee_prints(
        congress: int | None = None,
        print_type: str | None = None,
        print_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve committee print information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/CommitteePrintEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            print_type: Type of print
                - hprt: House Print
                - sprt: Senate Print
                - jprt: Joint Committee Print
            print_number: Specific print 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: Committee print data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/committee-print"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if print_type:
                url += f"/{print_type}"
                if print_number:
                    url += f"/{print_number}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for committee prints
        }
    
        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 committee print information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:496-496 (registration)
    The @mcp.tool() decorator registers the get_committee_prints function as an MCP tool.
    @mcp.tool()
  • Input schema defined by function parameters with type annotations and detailed docstring describing arguments and return type.
    async def get_committee_prints(
        congress: int | None = None,
        print_type: str | None = None,
        print_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve committee print information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/CommitteePrintEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            print_type: Type of print
                - hprt: House Print
                - sprt: Senate Print
                - jprt: Joint Committee Print
            print_number: Specific print 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: Committee print 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. While it mentions the API endpoint and parameter defaults, it doesn't describe important behavioral aspects: whether this is a read-only operation, what authentication might be required, rate limits, error conditions, or what the returned data structure looks like. The link to external documentation is helpful but doesn't substitute for self-contained behavioral description.

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. Every sentence earns its place, though the external documentation link could be more integrated. The description is appropriately sized for a 7-parameter tool without unnecessary verbosity.

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 the tool's complexity (7 parameters, no annotations, no output schema), the description is moderately complete. It excels at parameter documentation but lacks behavioral context and output details. The absence of annotations means the description should cover more about the tool's operational characteristics, but it doesn't fully address this gap despite the parameter coverage.

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?

The description provides excellent parameter semantics despite 0% schema description coverage. It clearly explains all 7 parameters with examples (e.g., '118 for 118th Congress'), enumerated values for print_type (hprt, sprt, jprt), format specifications (YYYY-MM-DDTHH:MM:SSZ), and practical constraints (max 250 records). This fully compensates for the lack of schema descriptions.

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 committee print information from the Congress.gov API.' It specifies the resource (committee prints) and verb (retrieve). However, it doesn't explicitly differentiate this tool from its siblings like get_committee_reports or get_hearings, which also retrieve congressional documents.

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. It mentions a link to full documentation but gives no explicit context about when this specific tool is appropriate compared to sibling tools like get_committee_reports or get_hearings. There's no mention of prerequisites, constraints, or typical use cases.

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