Skip to main content
Glama
amurshak

CongressMCP-full

Treaties and Summaries - Legislative treaties and bill summaries

treaties_and_summaries

Access U.S. treaties and bill summaries from Congress.gov. Retrieve treaty texts, view legislative actions and committee assignments, and search bill summaries by keyword, congress, or date range.

Instructions

Treaties and Summaries Tool - Focused access to treaties and bill summaries.

TREATIES OPERATIONS:
• Search & Discovery: search_treaties
• Legislative Process: get_treaty_actions, get_treaty_committees
• Content: get_treaty_text

SUMMARIES OPERATIONS:
• Search & Discovery: search_summaries

TREATIES:
- search_treaties: Find treaties by congress and parameters
- get_treaty_actions: Legislative actions on treaties
- get_treaty_committees: Committee assignments for treaties
- get_treaty_text: Full treaty text and resolutions

SUMMARIES:
- search_summaries: Search bill summaries by keywords and congress

Args:
    operation: Specific operation to perform (see list above)
    congress: Congress number (118 for current, 119 for next)
    treaty_number: Specific treaty number within congress
    treaty_suffix: Treaty suffix identifier
    keywords: Search keywords for content
    topic: Topic filter for summaries
    limit: Results limit (max 250 for API compliance)
    sort: updateDate+desc (newest first) or updateDate+asc
    fromDateTime/toDateTime: Date range (YYYY-MM-DDTHH:MM:SSZ)
    
Returns:
    Formatted results specific to requested operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
congressNo
treaty_numberNo
treaty_suffixNo
keywordsNo
topicNo
limitNo
sortNo
formatNo
offsetNo
fromDateTimeNo
toDateTimeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully documents the API compliance limit (max 250) and date format constraints (YYYY-MM-DDTHH:MM:SSZ), but fails to disclose safety characteristics (read-only vs. destructive), rate limiting behavior, or error handling patterns.

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

Conciseness3/5

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

The description suffers from structural redundancy, listing operations twice (bullet points under 'TREATIES OPERATIONS' and dash list under 'TREATIES'). The Args section is well-structured, but the opening 'Treaties and Summaries Tool' restates the title without adding value.

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 polymorphic tool with 12 parameters and an output schema, the description is incomplete. It fails to enumerate valid values for the required 'operation' parameter (only referring to 'list above'), does not describe the output format despite the presence of an output schema, and omits documentation for two parameters.

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?

Given 0% schema description coverage, the description compensates well by explaining 10 of 12 parameters, including specific enum-like values for 'sort' (updateDate+desc/asc) and congress number examples (118, 119). However, it omits explanations for 'format' and 'offset' parameters.

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 identifies the tool provides 'Focused access to treaties and bill summaries' and enumerates specific operations (search_treaties, get_treaty_text, etc.). However, it does not clearly differentiate when to use this tool versus the sibling 'bills' tool for bill summary access.

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?

While the description lists available operations grouped by category (Search & Discovery, Legislative Process, Content), it provides no guidance on when to use this tool versus alternatives like 'bills', nor does it specify prerequisites or selection criteria for choosing between operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

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