Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_congress

Retrieve U.S. Congress information from the official Congress.gov API. Specify a congress number or get all data with pagination controls.

Instructions

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

Args: congress: Specific congress number (e.g., 118 for 118th Congress) or None for all offset: Starting record (default 0) limit: Maximum records to return (max 250, default 20)

Returns: dict: Congress data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNo
offsetNo
limitNo

Implementation Reference

  • The handler function decorated with @mcp.tool(), implementing the 'get_congress' tool by querying the Congress.gov API for congress data based on parameters like congress number, offset, and limit.
    @mcp.tool()
    async def get_congress(
        congress: int | None = None,
        offset: int = 0,
        limit: int = 20
    ) -> dict:
        """
        Retrieve congress information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/CongressEndpoint.md
    
        Args:
            congress: Specific congress number (e.g., 118 for 118th Congress) or None for all
            offset: Starting record (default 0)
            limit: Maximum records to return (max 250, default 20)
    
        Returns:
            dict: Congress data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/congress"
    
        url = base_url
        if congress:
            url += f"/{congress}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for congress
        }
    
        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 congress information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:227-227 (registration)
    The @mcp.tool() decorator registers the get_congress function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the API endpoint and provides a link to documentation, but doesn't disclose key behavioral traits: whether this is a read-only operation, rate limits, authentication requirements, error handling, or what specific data fields are returned. The description is minimal beyond basic functionality.

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 appropriately sized and well-structured with clear sections (Args, Returns). The first sentence states the purpose, followed by documentation link and parameter details. Every sentence adds value, though the documentation link could be more integrated rather than standalone.

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 3-parameter tool with no annotations and no output schema, the description provides basic parameter semantics and return type indication ('dict: Congress data'). However, it lacks details about the structure of returned data, error cases, authentication, or how it differs from sibling tools, leaving significant gaps for an agent to use it effectively.

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 compensates well by explaining all three parameters: 'congress' (specific number or None for all), 'offset' (starting record), and 'limit' (max records with constraints). It provides practical examples and constraints beyond what the bare schema shows, though it doesn't explain parameter interactions or validation rules.

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 congress information from the Congress.gov API.' It specifies the verb ('retrieve') and resource ('congress information'), though it doesn't explicitly differentiate from siblings like 'get_members' or 'get_committees' which retrieve different types of congressional data.

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 many sibling tools retrieving different congressional data types (e.g., bills, members, committees), there's no indication of what 'congress information' specifically includes or when to choose this over other 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