Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Get Member Cosponsored Legislation - Bills and resolutions cosponsored by a member

get_member_cosponsored_legislation

Retrieve bills and resolutions cosponsored by a specific member of Congress using their bioguide ID. Supports pagination with limit and offset for browsing results.

Instructions

Get legislation cosponsored by a specific member of Congress.

Args:
    ctx: Context for API requests
    bioguide_id: Unique bioguide identifier for the member
    limit: Maximum number of cosponsored bills to return
    offset: Zero-based offset for pagination

Returns:
    List of bills and resolutions cosponsored by the member

Input Schema

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

A4.1/5.0
Behavior3/5

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

No annotations are present, so the description carries more weight. It discloses the read-only nature through the verb 'Get' and the 'Returns' section, and it exposes pagination behavior via offset and limit. However, it does not explicitly confirm no side effects, mention permissions, or describe any error/rate-limit behavior.

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 compact, well-organized into Args and Returns sections, and the core purpose is front-loaded in the first sentence. Every section earns its place with no filler or repetition.

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 read-only lookup, the description is nearly complete: all user-supplied parameters are described and the output schema covers return shape. The main gap is that it doesn't explicitly route the agent to get_member_sponsored_legislation when sponsored bills are needed, and the mention of 'ctx' might be slightly confusing since it is not in the input schema.

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 input schema has 0% property descriptions, but the description fully compensates by explaining all three parameters: bioguide_id is the unique member identifier, limit is the maximum number of bills, and offset is zero-based pagination. This adds meaningful semantics beyond the raw JSON schema.

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 opens with 'Get legislation cosponsored by a specific member of Congress,' which names a specific verb, resource, and scope. The use of 'cosponsored' clearly distinguishes this from sibling tool get_member_sponsored_legislation.

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 the tool should be used when the agent needs bills/resolutions cosponsored by a particular member, but it does not explicitly state when to use this tool versus alternatives like get_member_sponsored_legislation. There are no exclusions or when-not-to-use conditions.

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