Skip to main content
Glama
Bosco Labs Data

Bosco Labs Data

Official

US House stock trades

search_us_house_stock_trades
Read-only

Search STOCK Act disclosures to find US House members' stock, option, fund, and bond trades by member, ticker, transaction type, or filing date; returns trade details and source filing PDF links.

Instructions

Stock, option, fund and bond trades disclosed by members of the US House of Representatives under the STOCK Act (Periodic Transaction Reports), from January 2014 to today (source: official filings of the Clerk of the House). Use it for "what did Representative X trade", "which House members traded NVDA", or recent congressional trades.

Filter by member name, tickers, transaction type and filing date (default: the last 30
days); use `years` for older history. Newest filings first.

Returns one row per trade: member_name, state_district, filing_date, transaction_date,
days_to_disclose, owner (self, spouse, joint, child), ticker, asset_description,
asset_type, transaction_type, amount_min/amount_max (USD range as filed), amount_text,
is_amendment and pdf_url (the filing; cite it). Amounts are ranges, not exact values.
The Senate is not covered.

Cost to the user: $0.0018 per trade returned.

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": "search_us_house_stock_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoWhole filing years for history, e.g. [2020, 2021]
membersNoPart of the member name, e.g. "Pelosi"
tickersNo
filed_toNo
filed_fromNoDefault: 30 days ago
max_resultsNoMax trades to return (1-100).
min_amount_usdNoe.g. 15001 skips the $1,001-$15,000 range
transaction_typesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-annotation context: newest-filings-first ordering, per-trade cost of $0.0018, amounts being ranges rather than exact values, amendment rows, and a pdf_url to cite. Deducting because the cost and ordering are the only operational traits beyond that, and nothing is said about pagination or what happens when max_results truncates a large result set.

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 purpose, then filters, then return shape, then cost — a sensible order with no filler sentences. It runs somewhat long, partly because it enumerates return fields that the output schema already defines.

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?

Covers source provenance, coverage window, default behavior, cost model, and the semantic caveat that amounts are ranges — everything an agent needs to call this correctly and to caveat its answer. The output-schema duplication is redundant but harmless.

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?

At 63% schema coverage the description usefully clarifies that date filters apply to filing date with a 30-day default and that `years` is the escape hatch for older history. It does not touch min_amount_usd or max_results, both of which carry schema descriptions anyway, so the remaining gap is modest.

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?

Specific verb+resource with explicit scope: House members' STOCK Act disclosures from official Clerk filings, 2014–today. It also draws the boundary that 'the Senate is not covered', which an agent needs to avoid mis-scoping a congressional-trades request.

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

Usage Guidelines4/5

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

Concrete example queries ('what did Representative X trade', 'which House members traded NVDA') plus a rule for the temporal alternative ('use `years` for older history') and the 30-day default. It never distinguishes itself from the sibling search_sec_insider_trades, which is the most likely point of confusion, so it falls short of full when-not guidance.

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