Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_house_requirement

Retrieve House requirement data from Congress.gov API by specifying congress number, requirement details, or date ranges for legislative research.

Instructions

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

Args: congress: Congress number (e.g., 118 for 118th Congress) requirement_number: Specific requirement 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 requirement data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
requirement_numberNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo

Implementation Reference

  • The core handler function for the 'get_house_requirement' tool. It is decorated with @mcp.tool(), which automatically generates the schema from type hints and docstring, and registers the tool with the MCP server. The function constructs a URL and parameters for the Congress.gov API and fetches the data.
    @mcp.tool()
    async def get_house_requirement(
        congress: int | None = None,
        requirement_number: int | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None
    ) -> dict:
        """
        Retrieve House requirement information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/HouseRequirementEndpoint.md
    
        Args:
            congress: Congress number (e.g., 118 for 118th Congress)
            requirement_number: Specific requirement 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 requirement data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/house-requirement"
    
        url = base_url
        if congress:
            url += f"/{congress}"
            if requirement_number:
                url += f"/{requirement_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 requirement 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 endpoint and return format ('dict: House requirement data'), but lacks critical behavioral details: whether this is a read-only operation, what authentication might be required, rate limits, error handling, or what specific data structure is returned. The external documentation link partially compensates but isn't self-contained.

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?

Well-structured with purpose statement, documentation link, parameter details, and return format. The Args/Returns sections are clearly organized. Slightly verbose with the full URL, but each sentence serves a purpose. Could be more front-loaded by moving the return format closer to the purpose statement.

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 6-parameter tool with no annotations and no output schema, the description does reasonably well on parameters but lacks behavioral context. The external documentation link helps but creates dependency. Without understanding what 'House requirement' data contains or how it differs from other congressional data, an agent might struggle to use this appropriately versus siblings.

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. Each of the 6 parameters gets clear explanations with examples (e.g., '118 for 118th Congress'), format specifications ('YYYY-MM-DDTHH:MM:SSZ format'), and constraints ('max 250, default 20'). This adds substantial value beyond the bare schema.

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 'House requirement information from the Congress.gov API', making the purpose unambiguous. It doesn't explicitly differentiate from siblings like get_bills or get_committees, but the specificity of 'House requirement' provides inherent distinction. The link to external documentation adds precision but doesn't fully substitute for sibling differentiation.

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?

No guidance is provided about when to use this tool versus alternatives like get_bills or get_house_votes. The description mentions the API endpoint but doesn't explain what 'House requirement' means or when this specific data type would be needed versus other congressional data types available in sibling tools.

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