Skip to main content
Glama
AshwinSundar

Congress[.]gov MCP Server

by AshwinSundar

get_members

Retrieve U.S. Congress member details using bioguide IDs, date ranges, or current status filters to access official legislative data.

Instructions

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

Args: bioguide_id: Specific member bioguide ID (e.g., "A000374") 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) current_member: Filter by current member status (true/false)

Returns: dict: Member data from Congress.gov API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioguide_idNo
offsetNo
limitNo
from_datetimeNo
to_datetimeNo
current_memberNo

Implementation Reference

  • The handler function for the 'get_members' MCP tool. It is registered via the @mcp.tool() decorator and implements the logic to fetch member data from the Congress.gov API using requests, handling parameters like bioguide_id, pagination, date ranges, and current member filter.
    async def get_members(
        bioguide_id: str | None = None,
        offset: int = 0,
        limit: int = 20,
        from_datetime: str | None = None,
        to_datetime: str | None = None,
        current_member: bool | None = None
    ) -> dict:
        """
        Retrieve member information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/MemberEndpoint.md
    
        Args:
            bioguide_id: Specific member bioguide ID (e.g., "A000374")
            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)
            current_member: Filter by current member status (true/false)
    
        Returns:
            dict: Member data from Congress.gov API
        """
        base_url = "https://api.congress.gov/v3/member"
    
        url = base_url
        if bioguide_id:
            url += f"/{bioguide_id}"
    
        params = {
            "api_key": congress_gov_api_key,
            "format": "json",
            "offset": offset,
            "limit": min(limit, 250)  # API max limit for members
        }
    
        if from_datetime:
            params["fromDateTime"] = from_datetime
        if to_datetime:
            params["toDateTime"] = to_datetime
        if current_member is not None:
            params["currentMember"] = str(current_member).lower()
    
        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 member information: {str(e)}",
                "status_code": getattr(e.response, "status_code", None)
            }
  • server.py:18-18 (registration)
    Initialization of the FastMCP server instance where tools like get_members are registered via decorators.
    mcp = FastMCP("usgov_mcp")
  • The docstring and type annotations in the function signature define the input schema and output type for the get_members tool.
    """
    Retrieve member information from the Congress.gov API. Full documentation for this endpoint -> https://github.com/LibraryOfCongress/api.congress.gov/blob/main/Documentation/MemberEndpoint.md
    
    Args:
        bioguide_id: Specific member bioguide ID (e.g., "A000374")
        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)
        current_member: Filter by current member status (true/false)
    
    Returns:
        dict: Member 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 the full burden of behavioral disclosure. While it mentions the API endpoint documentation link and describes some parameter behaviors (defaults, max values), it doesn't disclose important behavioral traits like rate limits, authentication requirements, error handling, pagination behavior beyond offset/limit, or what happens when multiple filters conflict. The description is functional but lacks comprehensive behavioral context.

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 efficiently communicates essential information. While the external documentation link adds value, the description itself is appropriately sized and front-loaded with the core purpose. Every sentence serves a clear function in explaining the tool's usage.

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 complexity (6 parameters, no annotations, no output schema), the description provides solid parameter documentation but lacks complete behavioral context. The return value description ('dict: Member data from Congress.gov API') is minimal without explaining the structure or content of the returned data. For a tool with multiple filtering parameters and no output schema, more detail about the response format would be helpful.

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 that fully compensate for the 0% schema description coverage. It clearly explains each of the 6 parameters with specific examples ('A000374'), format requirements ('YYYY-MM-DDTHH:MM:SSZ'), constraints ('max 250'), defaults, and filtering logic. This goes well beyond what the bare schema provides and gives the agent practical guidance on how to use each parameter effectively.

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 ('member information from the Congress.gov API'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its many siblings (like get_committees or get_bills), which all appear to 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 19 sibling tools that all retrieve different congressional data types, there's no indication of what distinguishes member information retrieval from other data types or when an agent should choose this specific tool.

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