Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Get Member Details - Detailed information about a specific member of Congress

get_member_details

Look up a member of Congress by Bioguide ID to access detailed biographical data and complete term history.

Instructions

Get detailed information about a specific member of Congress.

Args:
    ctx: Context for API requests
    bioguide_id: Unique bioguide identifier for the member (e.g., 'B000944')

Returns:
    Detailed member information including biographical data, terms served, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioguide_idYes

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

B3.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 full burden. It does disclose the return behavior ('detailed member information including biographical data, terms served, etc.') and the 'Get' verb implies a read operation. However, it does not mention error behavior, data limitations, or any other non-obvious traits.

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 short and organized into Args and Returns sections, making the purpose easy to scan. The inclusion of 'ctx' as an argument is unnecessary and potentially confusing, and the Returns section repeats some of the opening phrasing, but overall there is little waste.

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 one-parameter read-only tool, the description is minimally adequate and an output schema is present. However, given the large sibling list, the description would benefit from explicit guidance on when this tool is the right choice versus get_members_by_congress, search_members, or other member-related tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds useful meaning for bioguide_id by calling it 'Unique bioguide identifier' and providing an example, which goes beyond the bare schema. However, it also lists 'ctx' as an argument even though ctx is not in the input schema, which could mislead an agent into passing an invalid parameter.

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 a specific verb and resource: 'Get detailed information about a specific member of Congress.' The phrase 'specific member' helps distinguish it from list-oriented siblings like get_members_by_state or search_members, though it does not explicitly name or contrast them.

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?

No guidance is given about when to use this tool vs. alternatives. There is no mention of using search_members if the bioguide_id is unknown, or using get_member_sponsored_legislation for sponsored bills. The intended use is only implied by the tool name and the required parameter.

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