Skip to main content
Glama
mainfraame

cigar-butt

by mainfraame
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search congressional trades by ticker

congress_trades
Read-only

Search disclosed Senate stock transactions by ticker, member, or both to see who traded a stock, when, and which committees they sit on.

Instructions

Search disclosed Senate stock transactions by ticker, by member, or both. No credential needed. This is the natural entry point: ask "who in the Senate traded ASTE?" and get every disclosed transaction in the index, with the committees each member sits on.

eFD itself cannot be searched by ticker — its form takes a filer name, a state and a filing-date window and nothing else — so transactions are held in a local index. It refreshes itself when stale, and reports are immutable once filed, so keeping current costs only the new filings. Use congress_index to see how deep the index reaches and to backfill further; a search can only find what has been indexed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
memberNoFilter by senator name; matched as a substring.
tickerNoTicker to search for, e.g. "NVDA". Bonds, funds and private holdings often have no ticker and will not match.
sinceDaysNoOnly transactions this recent, by transaction date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only and open-world, but the description adds substantial non-obvious context: no credential required, an eFD limitation that forces a local index, self-refresh-on-stale behavior, immutability of filed reports, and the critical caveat that a search only finds what has been indexed.

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-loads the core search capability in the first sentence, then justifies the local-index design. The eFD internals paragraph is slightly long but earns its place by explaining the freshness caveat.

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 no output schema, the description helpfully previews the return content ('every disclosed transaction... with the committees each member sits on') and covers freshness and index depth. It is silent on pagination/limit behavior and result ordering.

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 75% and already documents ticker, member, and sinceDays. The description reinforces that filters are combinable but adds no syntax, matching, or defaulting detail beyond the schema, so baseline 3 applies.

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 (search disclosed Senate stock transactions) plus scope (by ticker, by member, or both), and names the sibling congress_index it is distinct from. An agent can identify the tool's job without opening the schema.

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?

Explicitly frames itself as 'the natural entry point' with a concrete example query, and routes index-depth/backfill questions to congress_index. It does not explicitly bound itself against the House-oriented sibling congress_house_filings, leaving that boundary to be inferred from 'Senate'.

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

Deploy Server

Other Tools