Skip to main content
Glama

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Congressional Trades by Stock

GetCongressionalTrades
Read-only

Get congressional securities transactions for a specific ticker (newest first, last year by default). Shows which members of Congress reported a purchase or sale, with transaction and filing dates; amounts are disclosed ranges, not exact values, and Asset identifies the filed instrument (such as stock, option, or bond). Use GetMemberTrades for one member's transactions across all tickers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoNumber of matching trades to skip before returning rows (default: 0)
tickerYesListed security ticker (e.g., AAPL, VOO, MSFT)
endDateNoEnd date in YYYY-MM-DD format (defaults to today)
startDateNoStart date in YYYY-MM-DD format (defaults to 1 year ago)
maxResultsNoMaximum number of trades to return (default: 50, max: 500, newest first)
transactionTypeNoFilter by transaction type: Purchase or Sale; the synonyms Buy/Sell are accepted (defaults to all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol (e.g., AAPL, MSFT, NVDA)"New value: +"Listed security ticker (e.g., AAPL, VOO, MSFT)"
  2. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of matching trades to skip before returning rows (default: 0)",
+  "type": "integer"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, and the description adds several useful behavioral details: results are newest first, the default lookback is one year, transaction amounts are disclosed ranges rather than exact values, and Asset refers to the filed instrument type. These are exactly the kind of behavioral nuances that prevent misinterpretation beyond what annotations convey.

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?

Three sentences, no filler, with the core action and defaults front-loaded before the alternative routing. Every sentence earns its place.

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?

Given there is no output schema, the description compensates well by describing what the response contains: members of Congress, transaction and filing dates, amount ranges, and the Asset field. Combined with thorough parameter schemas and a clear sibling pointer, nothing essential is missing for correct invocation and interpretation.

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 the baseline is 3 because the schema already documents all parameters clearly. The description adds little beyond what the schema states; it echoes 'specific ticker' and 'last year by default' but does not materially enhance understanding of offset, maxResults, or transactionType.

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?

The description states a specific verb and resource: getting congressional securities transactions for a specific ticker. It also clearly differentiates from the sibling GetMemberTrades by scoping this tool to one ticker, so an agent can select it without inspecting 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 Guidelines5/5

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

The description explicitly names GetMemberTrades as the alternative for one member's transactions across all tickers, giving a clear routing condition. This tells the agent when to use this tool versus that sibling, which is strong usage guidance.

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

All Equibles toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources