Skip to main content
Glama

get_congress_trades

Read-onlyIdempotent

Search individual stock trades disclosed by U.S. Congress members (House and Senate) under the STOCK Act. Returns a markdown table of transactions: member name, chamber, ticker, buy/sell type, transaction date, disclosure date (the gap between the two reveals reporting delay), dollar amount range, and owner (self/spouse/joint). Use for questions like 'What did Nancy Pelosi trade recently?', 'Which members bought NVDA?', or 'Show the largest Senate trades this quarter'. Filter by chamber, ticker, or member name; sort by traded value, trade count, or recency. For one member's profile and complete trading history, use get_congress_member instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1)
sortNoSort order — volume (most traded value), trades (most trades), recent (latest first)volume
limitNoTrades per page, 1-50 (default 20)
searchNoFull or partial member name, e.g. 'Pelosi' or 'Dan Crenshaw'
tickerNoStock ticker symbol to filter by, e.g. NVDA or AAPL
chamberNoCongressional chamber: house, senate, or all (default all)all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYes
pagingYesPaging state reconciled from ko.io meta.total_count and meta.softwall
filtersYes
plan_limitYesThe Free/keyless plan limits ko.io applied to this answer (null for paid callers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "filters": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "chamber": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "search": {
      +          "$ref": "#/properties/filters/properties/chamber"
      +        },
      +        "sort": {
      +          "$ref": "#/properties/filters/properties/chamber"
      +        },
      +        "ticker": {
      +          "$ref": "#/properties/filters/properties/chamber"
      +        }
      +      },
      +      "required": [
      +        "chamber",
      +        "ticker",
      +        "search",
      +        "sort"
      +      ],
      +      "type": "object"
      +    },
      +    "paging": {
      +      "additionalProperties": false,
      +      "description": "Paging state reconciled from ko.io meta.total_count and meta.softwall",
      +      "properties": {
      +        "continuation": {
      +          "description": "SIGNIN_REQUIRED = page>1 needs a (free) ko.io API key",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "has_more": {
      +          "description": "null = a full page came back and more MAY exist",
      +          "type": [
      +            "boolean",
      +            "null"
      +          ]
      +        },
      +        "next_page": {
      +          "anyOf": [
      +            {
      +              "$ref": "#/properties/paging/properties/total_count/anyOf/0"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Next page THIS caller can open; null when there is none (or sign-in is required)"
      +        },
      +        "page": {
      +          "type": "integer"
      +        },
      +        "per_page": {
      +          "type": "integer"
      +        },
      +        "plan_row_cap": {
      +          "anyOf": [
      +            {
      +              "$ref": "#/properties/paging/properties/total_count/anyOf/0"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Row cap the caller's plan applied to this page, if any"
      +        },
      +        "returned": {
      +          "type": "integer"
      +        },
      +        "total_count": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Total rows matching the request, when ko.io reported it"
      +        },
      +        "truncated_by_plan": {
      +          "description": "True when the plan's row cap withheld rows from this page",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "page",
      +        "per_page",
      +        "returned",
      +        "total_count",
      +        "has_more",
      +        "next_page",
      +        "continuation",
      +        "plan_row_cap",
      +        "truncated_by_plan"
      +      ],
      +      "type": "object"
      +    },
      +    "plan_limit": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "continuation": {
      +              "$ref": "#/properties/filters/properties/chamber"
      +            },
      +            "date_basis": {
      +              "$ref": "#/properties/filters/properties/chamber"
      +            },
      +            "effective_period": {
      +              "$ref": "#/properties/filters/properties/chamber"
      +            },
      +            "policy_version": {
      +              "$ref": "#/properties/filters/properties/chamber"
      +            },
      +            "row_cap": {
      +              "anyOf": [
      +                {
      +                  "$ref": "#/properties/paging/properties/total_count/anyOf/0"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "truncated": {
      +              "type": [
      +                "boolean",
      +                "null"
      +              ]
      +            },
      +            "window_end": {
      +              "$ref": "#/properties/filters/properties/chamber"
      +            },
      +            "window_start": {
      +              "$ref": "#/properties/filters/properties/chamber"
      +            }
      +          },
      +          "required": [
      +            "policy_version",
      +            "window_start",
      +            "window_end",
      +            "effective_period",
      +            "date_basis",
      +            "row_cap",
      +            "truncated",
      +            "continuation"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The Free/keyless plan limits ko.io applied to this answer (null for paid callers)"
      +    },
      +    "rows": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "amount_range": {
      +            "description": "The disclosed dollar RANGE (STOCK Act bands), not an exact amount",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "asset_description": {
      +            "$ref": "#/properties/filters/properties/chamber"
      +          },
      +          "chamber": {
      +            "$ref": "#/properties/filters/properties/chamber"
      +          },
      +          "disclosure_date": {
      +            "$ref": "#/properties/filters/properties/chamber"
      +          },
      +          "member_name": {
      +            "$ref": "#/properties/filters/properties/chamber"
      +          },
      +          "owner": {
      +            "$ref": "#/properties/filters/properties/chamber"
      +          },
      +          "ticker": {
      +            "$ref": "#/properties/filters/properties/chamber"
      +          },
      +          "transaction_date": {
      +            "$ref": "#/properties/filters/properties/chamber"
      +          },
      +          "transaction_type": {
      +            "$ref": "#/properties/filters/properties/chamber"
      +          }
      +        },
      +        "required": [
      +          "member_name",
      +          "chamber",
      +          "ticker",
      +          "asset_description",
      +          "transaction_type",
      +          "transaction_date",
      +          "disclosure_date",
      +          "amount_range",
      +          "owner"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "filters",
      +    "rows",
      +    "paging",
      +    "plan_limit"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / party
      Removed value: -{
      -  "default": "all",
      -  "description": "Filter by party — D=Democrat, R=Republican, I=Independent",
      -  "enum": [
      -    "D",
      -    "R",
      -    "I",
      -    "all"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / state
      Removed value: -{
      -  "description": "Member 2-letter U.S. state code, e.g. CA or TX",
      -  "maxLength": 200,
      -  "type": "string"
      -}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already declare readOnly/openWorld/idempotent/non-destructive behavior, so the bar is lower, but the description still adds concrete behavioral context: it returns a markdown table, highlights that the disclosure-date gap reveals reporting delay, and lists owner categories. This tells the agent what kind of response to expect and what analytical value the data provides.

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?

The description is dense but every sentence earns its place: main purpose, return format, example queries, filter/sort semantics, and sibling differentiation. The most important information is front-loaded, and the length is appropriate for a search tool with six parameters and multiple use cases.

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?

With comprehensive annotations, a fully described input schema, and an output schema present, the description covers the remaining gap: when to use the tool, what it returns, and how to think about the data. An agent can confidently select and invoke this tool for a wide range of congressional-trade questions without needing additional context.

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 schema already documents every parameter. The description adds useful semantic framing by mapping the sort enum to plain-language meanings ('traded value, trade count, or recency'), demonstrating search examples, and showing how filters combine. It doesn't add new parameter details, but it makes the existing schema meanings easier to use.

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 opens with a specific verb and resource: 'Search individual stock trades disclosed by U.S. Congress members under the STOCK Act.' It names exact data fields (member, chamber, ticker, buy/sell, dates, amount range, owner) and even differentiates itself from the sibling get_congress_member by explicitly indicating that the sibling covers one member's profile and complete history.

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?

Usage guidance is explicit and actionable: it lists representative questions ('What did Nancy Pelosi trade recently?'), describes filter and sort options, and names the alternative tool with the condition for choosing it ('For one member's profile and complete trading history, use get_congress_member instead'). This leaves no ambiguity about when to call this tool versus its sibling.

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.