Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Get Committee Communications - Communications received by a specific committee

get_committee_communications

Retrieve letters and statements issued by a specific congressional committee. Use the committee code to access its communications, with options for chamber, pagination, and newest-first sorting.

Instructions

Get communications (letters, statements) from a specific committee.

Args:
    ctx: Context for API requests
    committee_code: Official committee code (e.g., 'hsju', 'ssju')
    chamber: Chamber of Congress ("house", "senate", or "joint").
             If omitted, inferred automatically from the committee code prefix.
    limit: Maximum number of communications to return
    offset: Starting record (0-based) for explicit paging.
    most_recent: When True (default), return the newest communications first.

Returns:
    List of communications from the committee

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
chamberNo
most_recentNo
committee_codeYes

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.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does disclose pagination semantics (offset is 0-based), the default ordering behavior (most_recent=True returns newest first), and automatic chamber inference. However, it does not mention potential errors, data availability limitations, or whether the operation is strictly read-only, though 'Get' implies this.

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 one-sentence purpose statement followed by a compact Args list and Returns line. Each line adds useful information, and there is no padding or repetition of the schema.

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?

With an output schema present, the description does not need to detail return fields. It covers all five parameters, provides defaults and inference behavior, and includes a clear return description. It is sufficiently complete for an agent to invoke the tool correctly, though it could add a small note about when the committee_code format may be invalid.

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 description must compensate. It does so by explaining committee_code with concrete examples, describing chamber inference behavior, and clarifying limit, offset, and most_recent semantics beyond the bare schema definitions. This adds real meaning to every parameter.

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 ('communications (letters, statements)'), and a specific scope ('from a specific committee'). This distinguishes it from sibling committee tools like get_committee_bills and get_committee_reports, which target different resource types.

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 intended use is implied by the title and description: call this when you need communications from a specific committee. However, the description does not explicitly mention alternatives or provide when-to-use versus when-not-to-use guidance against the many sibling committee tools.

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