Skip to main content
Glama

get_congress_trades

U.S. House Clerk and Senate eFD STOCK Act periodic transaction disclosures by ticker or member name with disclosed dollar brackets. $0.02.

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
limitNoMaximum trades to return (default 20, max 50)
sinceNoOptional ISO-8601 cutoff timestamp
personNoCongress member name filter (e.g. Pelosi)
tickerNoUS stock ticker filter (e.g. NVDA)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden alone. It does add real value by identifying the authoritative sources and the fact that amounts are disclosed as dollar brackets (not exact figures), plus a terse '$0.02' cost signal that hints at per-call billing; however, it says nothing about permissions, rate limits, result ordering, or pagination behavior.

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?

A single front-loaded sentence conveys source, subject matter, filter axes, and the dollar-bracket caveat, followed by a compact cost marker. Nothing is padded, though the trailing '$0.02' is cryptic enough to cost a little clarity.

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?

For a four-optional-parameter lookup tool with no output schema, the description covers provenance, subject, filter options, and the shape of the disclosed values well enough to call it correctly. The main gap is the absence of any statement about return ordering or what happens when both filters are omitted.

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%, so all four parameters already carry inline docs including defaults and examples. The description restates the two filter axes (ticker, member name) without adding format or precedence guidance, so the baseline 3 applies.

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 states a specific verb+resource: 'STOCK Act periodic transaction disclosures' from 'U.S. House Clerk and Senate eFD', with two named access paths (ticker or member name). That is far more specific than the bare name, though it never names a sibling such as get_insider_trades to draw the corporate-insider vs. congressional boundary explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: naming the House Clerk and Senate eFD sources signals 'congressional disclosures' as opposed to corporate insider filings, so an agent can reason about the alternative. There is no explicit when-to-use/when-not-to-use clause or reference to any alternative tool.

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