Skip to main content
Glama

senate_trades_by_ticker

Get US Senate stock trades for any ticker, including transaction dates, senators, trade types, amounts, and disclosure lags to track lawmaker trading activity.

Instructions

Normalized US Senate trades: { format: "json", ticker, name, series: [{date, senator, trade_type, amount_min, amount_max, amount_exact, amount_raw, disclosure_date, owner, amount_as_filed, amount_flag}, ...], series_count, series_total } date is the transaction date; disclosure_date is when the trade was publicly disclosed in the member's periodic transaction report. The gap between them is the reporting lag. owner is the beneficial owner of the traded account: "SELF", "SP" (spouse), "DC" (dependent child), "JT" (joint), an account code, or "UNKNOWN" for blank Senate filings. owner and disclosure_date are nullable, though rare — historical rows were backfilled upstream. amount_raw is the amount string as served by the API, normalized to a statutory STOCK Act bracket when the filed string is an unambiguous variant of one; amount_as_filed then preserves the original filing. amount_flag is "review" or "ambiguous" when the filed amount could not be safely normalized (amount_raw keeps the filed string, or "Unknown"); both are null on all other rows. CSV returns the sliced series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reqYes
Behavior3/5

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

With no annotations, the description must disclose behavior itself. It explains output semantics (date lag, owner codes, amount normalization) and the CSV behavior, but omits operational details like rate limits, authentication, or pagination. It does not contradict annotations but is incomplete on behavioral traits.

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 is quite long and dives deep into output field semantics, which is useful given no output schema, but it lacks a front-loaded summary. It spends many sentences on edge cases (amount_flag, owner) that could be condensed without losing essential guidance.

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?

Given the rich output structure and absence of an output schema, the description adequately documents the returned data. However, it overlooks practical context such as how to use the 'limit' parameter, whether results are paginated, or the meaning of the series object. Overall, it is more complete on output than on usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the key parameters (ticker, limit, date_from, date_to) beyond the schema's minimal date descriptions. It mentions 'format' in the output sample but not as a parameter choice. Schema coverage is low, so the description should compensate, but it focuses on output fields instead.

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 states it returns normalized US Senate trades, with a specific resource (ticker) and verb implied by the data structure. It distinguishes from siblings like house_trades_by_ticker via the name itself, though the description does not explicitly call out alternatives.

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?

No guidance on when to use this tool versus alternatives (e.g., house_trades_by_ticker or screener tools). It does not mention prerequisites, use cases, or exclusions, leaving the agent to infer from the name.

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/ahmetsbilgin/finbrain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server