Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Get Members by State - Current or historical representatives from a specific state

get_members_by_state

Retrieve congressional members by two-letter state code, with options to show current members only and limit returned results.

Instructions

Get members of Congress from a specific state.

Args:
    ctx: Context for API requests
    state_code: Two-letter state code (e.g., 'CA', 'TX', 'NY')
    current_member: Whether to only show current members (defaults to True)
    limit: Maximum number of members to return

Returns:
    List of members from the specified state

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
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
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It explains the current_member flag's effect (only show current members, defaulting to true) and that the call returns a list, giving the agent a clear read-only mental model. It does not discuss ordering, pagination, or invalid-state handling, but for a simple list endpoint this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is tight: a one-sentence summary, a labeled Args block with one line per parameter, and a one-line Returns note. No filler or duplicated schema noise.

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 simple three-parameter tool with an output schema, all parameters and the current/historical toggle are documented. The only notable omission is guidance on when to pick this over get_members_by_district or get_members_by_congress, but the state_code resource and sibling names make the distinction mostly recoverable.

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?

Schema coverage is 0%, so the description must compensate. It does: state_code is documented as a two-letter code with examples, current_member is given meaning and its default, and limit is clarified as the maximum number of returned members. The nullable current_member behavior is not elaborated, but the core semantics are clear.

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?

States a specific verb and resource: 'Get members of Congress from a specific state.' Title adds 'Current or historical representatives,' clarifying the main filtering dimension and distinguishing it from district- or congress-scoped siblings.

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

Usage Guidelines3/5

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

The description implies it should be used when members need to be retrieved by state_code, and the current_member parameter indicates a current-vs-historical choice. However, it never names or contrasts the many sibling member-lookup tools (by district, by congress, by congress+district), leaving the agent to infer when this tool is preferred.

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