Autario

congress_trades

Read-onlyIdempotent

Which US House members traded a stock, from their Periodic Transaction Reports (Clerk of the US House): member, date, purchase or sale, owner and official amount range, with totals of members, purchases and sales in the window. Works for companies on the autario company roster (trades are linked by the exact ticker the filer printed). Reports lag up to 45 days; Senate trades are not included.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "congress_trades"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max trades returned, newest first (default 200, max 2000).
`format`	No	Output wire format for this MCP call. Default 'toon' (Token-Oriented Notation, fewest tokens, best for tabular rows). 'compact' = minified JSON. 'json' = pretty JSON for readability. The REST API always returns JSON regardless.
`ticker`	Yes	Stock ticker, e.g. NVDA, AAPL, MSFT
`window`	No	30d \| 90d \| 1y \| 2y \| all (default 1y).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world lookup, so the description focuses on limitations the annotations cannot carry: 45-day reporting lag, exact-ticker linkage, roster coverage, and Senate exclusion. It does not discuss empty-result behavior for tickers with no congressional activity, which would be the last missing piece.

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?

Purpose is front-loaded in the first clause and the caveats are compressed into two short trailing sentences. The middle portion ('with totals of members, purchases and sales in the window') is slightly clunky but still informative rather than redundant.

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 usefully enumerates the return shape (member, date, purchase/sale, owner, amount range, aggregate totals). Combined with annotations covering safety, an agent has enough to decide and call, though edge-case behavior for uncovered tickers is unspecified.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics for 'ticker': trades are matched on the exact ticker string the filer printed and only for roster companies. It also clarifies what the 'window' governs (totals of members, purchases and sales in that window), which the schema does not state.

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 ('Which US House members traded a stock'), names the data source (Periodic Transaction Reports, Clerk of the US House), and enumerates the returned fields. The explicit 'US House' scoping separates it from the sibling get_politician_trades without the agent needing to open either 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?

Gives concrete applicability conditions: the ticker must be on the autario company roster, and Senate trades are out of scope (pointing implicitly to get_politician_trades). No explicit 'use X instead when...' routing sentence and no statement of what happens for an unsupported ticker, which keeps it below a 5.

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

All Autario tools Inspect

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

Need Help?