Skip to main content
Glama

FinanceQuery

Congressional Trades

get_congressional_trades
Read-onlyIdempotent

Get congressional trading disclosures for a symbol. Uses FMP when FMP_API_KEY is set, keyless House PTR filings otherwise.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_congressional_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds real behavioral context beyond that: the backend is data-source dependent — FMP when FMP_API_KEY is set, otherwise keyless House PTR filings — which implies results can differ in coverage and freshness between environments. It stops short of describing return shape or what the House-only fallback omits (e.g., Senate filings).

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?

Two tight sentences, with the core action front-loaded and the source-selection caveat second. Every clause carries information; there is no boilerplate or redundancy.

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 simple read-only, single-required-parameter lookup with full schema coverage and no output schema, the definition covers purpose and the environment-dependent data source. Minor gaps remain: it does not say whether pagination semantics differ between the two backends or what a caller sees when neither source returns data.

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 `symbol`, `limit`, `cursor`, and `fields` are already fully documented in the schema. The description adds nothing about parameter meaning or interaction (e.g., how pagination behaves across sources), so the baseline of 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 gives a specific verb and resource ('Get congressional trading disclosures for a symbol'), which is unambiguous and matches the required `symbol` parameter. It does not name or distinguish itself from any sibling, but the resource is distinct enough that confusion with tools like get_holders or get_insider-style siblings is unlikely.

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 only implied: the tool is scoped to a single symbol's congressional disclosures, which tells the agent when it applies. There is no explicit when-to-use/when-not-to-use statement and no named alternative for related data such as institutional holders, so guidance is adequate but thin.

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.