Equibles

Trades by Congress Member

GetMemberTrades

Read-only

Get a congress member's disclosed securities transactions (newest first, last year by default). Shows tickers, transaction and filing dates, disclosed amount ranges, the filed Asset identifying the instrument (such as stock, option, or bond), and the member's party on the transaction date. Use SearchCongressMembers to find member names, and GetCongressionalTrades for all members' transactions in one ticker.

Input Schema

Name	Required	Description
`offset`	No	Number of trades to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the clamped current offset; if the next offset exceeds 100000, narrow the filters instead. Stop when fewer than the effective page size (maxResults clamped to 1-500) are returned, or the response's total has been reached.
`ticker`	No	Optional stock ticker to combine with the member filter (e.g., AAPL)
`endDate`	No	End date in YYYY-MM-DD format (defaults to today)
`startDate`	No	Start date in YYYY-MM-DD format (defaults to 1 year ago)
`maxResults`	No	Maximum number of trades to return (default: 50, max: 500, newest first)
`memberName`	Yes	Congress member name, case-insensitive (e.g., 'Nancy Pelosi', 'Dan Crenshaw'); use SearchCongressMembers to find the exact name
`transactionType`	No	Filter by transaction type: Purchase or Sale; the synonyms Buy/Sell are accepted (defaults to all)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / offset / description

Previous value: -"Number of trades to skip before returning rows — pass the previous call's shown count to page past the maxResults cap (default: 0)"New value: +"Number of trades to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the clamped current offset; if the next offset exceeds 100000, narrow the filters instead. Stop when fewer than the effective page size (maxResults clamped to 1-500) are returned, or the response's total has been reached."

Changed1 schema field changedSep 3, 2026

addedInput schema / properties / ticker

Added value: +{
+  "default": null,
+  "description": "Optional stock ticker to combine with the member filter (e.g., AAPL)",
+  "type": "string"
+}

Changed1 schema field changedAug 9, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Number of trades to skip before returning rows — pass the previous call's shown count to page past the maxResults cap (default: 0)",
+  "type": "integer"
+}

First observedJul 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: default time window (last year), ordering (newest first), and the exact fields returned. It does not discuss pagination or rate limits, but the schema's offset/maxResults descriptions handle paging.

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?

Two tight sentences. The core purpose and default scope come first, followed by return fields, with sibling routing last. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description enumerates what is returned (tickers, transaction and filing dates, amount ranges, asset instrument, party), and the schema fully documents filtering and paging. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the schema already documents all seven parameters including pagination, date defaults, and the ticker/transactionType filters. The description only echoes the default one-year window and newest-first ordering, adding little beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb and resource (retrieves a congress member's disclosed securities transactions) plus scope (newest first, last year by default). It clearly distinguishes itself from the sibling tools GetCongressionalTrades and SearchCongressMembers.

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?

Explicitly routes the agent: use SearchCongressMembers to resolve member names, and GetCongressionalTrades for all members' transactions in a single ticker. The alternative and the condition that selects it are named, so no inference is required.

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

All Equibles tools Inspect

Try in Browser