Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Get Members by Congress - All members who served in a specific Congress

get_members_by_congress

Retrieve members of a specific U.S. Congress by number, with optional current-member filtering and result limits for precise legislative lookups.

Instructions

Get members who served in a specific Congress.

Args:
    ctx: Context for API requests
    congress: Congress number (e.g., 118 for 118th Congress)
    current_member: Whether to only show current members
    limit: Maximum number of members to return

Returns:
    List of members who served in the specified Congress

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
congressYes
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

A3.6/5.0
Behavior2/5

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

No annotations were provided, so the description carries the full burden of behavioral disclosure. It only says it returns a list and gives basic argument explanations; it does not clarify semantics like current_member=null vs false, pagination behavior, limit bounds, or the read-only nature of the operation.

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 compact and front-loads the core purpose before listing arguments and return type. The Args block partially duplicates the schema, but it adds useful explanatory text rather than just restating names, so the structure is appropriate and not bloated.

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?

With an output schema present, the return value does not need more explanation. However, with no annotations and minimal behavioral guidance, the description is only minimally complete for a three-parameter tool; missing edge-case semantics and alternative routing keep it from being fully contextual.

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 description coverage is 0%, so the parameter explanations in the description are valuable: congress gets an example (118), current_member is clarified as filtering to only current members, and limit is defined as a maximum. This compensates well for the schema's lack of descriptions, though it adds little about defaults, bounds, or null behavior.

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 ('members'), and a precise scope ('served in a specific Congress'). This cleanly differentiates it from sibling tools that get members by state, district, or combined congress/state/district.

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 usage context is implied by the name and description: use this when you need members for a particular Congress number. However, there is no explicit guidance about when to prefer this tool over nearby siblings, nor any conditions or exclusions, so it stays at the implied level.

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