Skip to main content
Glama
This connector has been deprecated

This connector has been replaced by OptimistFi, the same server under its official MCP Registry name com.optimistfi/optimistfi.

Congressional trades

get_congress_trades
Read-onlyIdempotent

House, Senate and President/officials stock trades (STOCK Act) by ticker or filer, dated by transaction. Use when the user asks: who in Congress traded X; what did a member or Trump buy. Not for: company insiders → get_insider_trades. Args: ticker or member; chamber; limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_congress_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost trades, newest first to return.
entityNoA company name, instead of a ticker.
memberNoA filer's name: what that member of Congress or official traded.
tickerNoA stock ticker: which members traded it.
chamberNo"house" (default), "senate" or "executive" (the President and Senate-confirmed officials): disclosures by ticker or filer; "all": the three together, by ticker.house

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / chamber / description
      Previous value: -"\"house\" (default): US House disclosures by ticker or member."New value: +"\"house\" (default), \"senate\" or \"executive\" (the President and Senate-confirmed officials): disclosures by ticker or filer; \"all\": the three together, by ticker."
    • changedInput schema / properties / member / description
      Previous value: -"A House member's name: what that member traded (House only)."New value: +"A filer's name: what that member of Congress or official traded."
  2. Changed5 schema fields changed
    • addedInput schema / properties / chamber / description
      Added value: +"\"house\" (default): US House disclosures by ticker or member."
    • addedInput schema / properties / entity / description
      Added value: +"A company name, instead of a ticker."
    • addedInput schema / properties / limit / description
      Added value: +"Most trades, newest first to return."
    • addedInput schema / properties / member / description
      Added value: +"A House member's name: what that member traded (House only)."
    • addedInput schema / properties / ticker / description
      Added value: +"A stock ticker: which members traded it."
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds provenance (STOCK Act disclosures) and the transaction-date basis, but says nothing about the reporting lag inherent to disclosure filings, result ordering beyond the schema note, or what happens when both member and chamber are supplied. Useful framing, but not much beyond the structured fields.

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?

Front-loaded with the resource definition, then usage triggers, exclusions, and arguments in a scannable order with no filler. The trailing 'Args:' line largely duplicates the schema, which keeps it from being perfectly economical.

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, full parameter coverage and rich annotations, the description only needs to carry purpose and routing, which it does well. It is slightly incomplete on how to combine ticker/member/chamber (e.g. that 'all' works by ticker) and on the effective requirement to pass at least one selector.

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?

Schema description coverage is 100%, including the chamber enum values and limit default, so the baseline is 3. The description's 'Args: ticker or member; chamber; limit' only echoes the schema and does not clarify whether ticker or member is effectively required, which is the one ambiguity an agent would face given zero required parameters.

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 names the resource precisely (House, Senate and President/officials stock trades under the STOCK Act), the two access axes (by ticker or filer), and the date basis (transaction date). It also names the sibling it is not, get_insider_trades, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit positive triggers ('who in Congress traded X; what did a member or Trump buy') and an explicit exclusion with the correct alternative ('Not for: company insiders → get_insider_trades'). This is textbook when/when-not/alternative guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources