Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_committee_reports

Retrieve committee report data from Congress.gov to access legislative information by congress, report type, number, or date range.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) report_type: Type of report - hrpt: House Report - srpt: Senate Report - erpt: Executive Report report_number: Specific report 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 report data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
report_typeNo
report_numberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The primary handler function for the 'get_committee_reports' MCP tool. It is decorated with @mcp.tool() which registers it as a tool. The function constructs API requests to Congress.gov for committee reports based on provided parameters and handles errors.
    @mcp.tool()
    async def get_committee_reports(
        congress: int | None = None,
        report_type: str | None = None,
        report_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve committee report information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/CommitteeReportEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            report_type: Type of report
                - hrpt: House Report
                - srpt: Senate Report
                - erpt: Executive Report
            report_number: Specific report 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 report data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/committee-report"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if report_type:
                url += f"/{report_type}"
                if report_number:
                    url += f"/{report_number}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for committee reports
        }
    
        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 report 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. While it mentions the API endpoint and provides parameter details, it doesn't describe important behavioral aspects like authentication requirements, rate limits, error handling, pagination behavior (beyond offset/limit parameters), or what happens when parameters are omitted. The link to external documentation partially compensates but doesn't provide immediate 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 enumerated values. It's appropriately sized for a 7-parameter tool, though the external documentation link could be considered extraneous. Every sentence earns its place by providing necessary information.

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 thoroughly documents parameters but lacks behavioral context and output details. The absence of an output schema means the description should ideally explain return values beyond 'Committee report data from Congress.gov API,' but it doesn't provide structure or examples of the returned data.

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 (titles only, no descriptions), the description provides excellent parameter semantics compensation. It clearly explains all 7 parameters with examples (e.g., '118 for 118th Congress'), enumerated values for report_type, format specifications (YYYY-MM-DDTHH:MM:SSZ), defaults, and constraints (max 250). 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 tool's purpose as 'Retrieve committee report information from the Congress.gov API,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate this tool from its many siblings (like get_committee_meetings, get_committee_prints, get_committees), which all retrieve different types of congressional data from the same API.

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 20 sibling tools available (including get_committee_meetings and get_committee_prints for similar committee-related data), there's no indication of what distinguishes committee reports from other committee outputs or when this specific retrieval is appropriate.

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