Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Get Member by Congress/State/District - Specific representative for a district in a Congress

get_members_by_congress_state_district

Identify the U.S. Representative who served a specific congressional district in a given Congress. Provide the congress number, state code, and district to retrieve the member's details.

Instructions

Get the member representing a specific congressional district in a specific Congress.

Args:
    ctx: Context for API requests
    congress: Congress number (e.g., 118 for 118th Congress)
    state_code: Two-letter state code (e.g., 'CA', 'TX', 'NY')
    district: Congressional district number within the state
    current_member: Whether to only include current members (default: True)

Returns:
    Member who represented the specified district in the specified Congress

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressYes
districtYes
state_codeYes
current_memberNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when success is false: the section-9 error envelope
itemsNoResults of other kinds (bills, reports, communications, nominations), as returned by Congress.gov
contextYesContext about the search or operation performed
membersNoMember results
successYesWhether the operation was successful
summaryYesHuman-readable summary of the results
item_kindNoWhat `items` contains (bill, committee_report, communication, nomination, ...)
operationYesThe operation that was performed
committeesNoCommittee results
results_countYesNumber of items returned (equals the populated list's length)
Install Server

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It explains the current_member filter default and states that a single member is returned, which is useful. However, it does not describe behavior when current_member is false, potential error cases, or whether historical members are included by default.

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 a clear one-sentence purpose, an Args block, and a Returns line. It is efficient, though the 'ctx' entry is an implementation detail not present in the schema and adds little for the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a straightforward lookup tool with an output schema available, the description covers purpose, parameters, defaults, and the return concept. It could be more complete with explicit guidance on choosing this over sibling get_members_by_* tools, but nothing essential to making the call is missing.

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?

Schema description coverage is 0%, but the description fully compensates by explaining each parameter: congress with an example, state_code with example values, district as the district number within the state, and current_member with its default meaning. This is exactly the added semantic value the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Get'), a clear resource ('the member representing a specific congressional district in a specific Congress'), and the exact combination of filters. This clearly distinguishes it from siblings like get_members_by_congress, get_members_by_state, and get_members_by_district, which each cover only a subset of these filters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The first sentence communicates exactly when to use this tool: when a single representative for a specific district in a specific Congress is needed. It does not explicitly contrast with sibling tools, but the precise scope and the sibling names make the intended use case clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/amurshak/congressMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server