Agent Einstein — Crypto & Market Intelligence

US Congress Stock Trades

get_congress_trades

Read-onlyIdempotent

Recently disclosed stock and asset transactions by members of the US Congress, newest first.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum rows to return (1-25).

Output Schema

Name	Required	Description
`count`	No	Disclosures in this pass.
`limit`	No	Row cap applied to every list in this payload.
`stale`	No	True when the snapshot is past its refresh interval.
`reason`	No	Why the payload is absent, when `available` is false.
`shorts`	No	Short signals.
`sources`	No	Per-source status — which filing feeds answered.
`available`	No	False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.
`fetchedAt`	No	When the underlying snapshot was refreshed (epoch ms or ISO-8601). Age matters: these are cached reads, not live queries.
`longSignals`	No	Scored buy-side signals.
`shortSignals`	No	Scored sell-side signals; same fields as `longSignals`.
`actionableLongs`	No	Long signals that cleared the scoring gate.
`sectorAggregates`	No	Disclosed dollars by sector.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedOutput schema / properties / fetchedAt / description

Previous value: -"When the underlying snapshot was refreshed (epoch ms, or ISO-8601 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries."New value: +"When the underlying snapshot was refreshed (epoch ms or ISO-8601). Age matters: these are cached reads, not live queries."

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "actionableLongs": {
+      "description": "Long signals that cleared the scoring gate."
+    },
+    "available": {
+      "description": "False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "count": {
+      "description": "Disclosures in this pass."
+    },
+    "fetchedAt": {
+      "description": "When the underlying snapshot was refreshed (epoch ms, or ISO-8601 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries."
+    },
+    "limit": {
+      "description": "Row cap applied to every list in this payload.",
+      "type": "number"
+    },
+    "longSignals": {
+      "description": "Scored buy-side signals.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "band": {
+            "description": "Score band."
+          },
+          "earliestTxAt": {
+            "description": "Earliest transaction date — filings lag trades."
+          },
+          "headline": {
+            "description": "One-line summary."
+          },
+          "lawmakerCount": {
+            "description": "Distinct filers."
+          },
+          "rationale": {
+            "description": "Why it scored where it did."
+          },
+          "score": {
+            "description": "Conviction score, 0-1."
+          },
+          "ticker": {
+            "description": "Equity ticker."
+          },
+          "totalUsd": {
+            "description": "Disclosed USD behind the signal."
+          }
+        }
+      },
+      "type": "array"
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "sectorAggregates": {
+      "description": "Disclosed dollars by sector.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "count": {
+            "description": "Disclosures."
+          },
+          "sector": {
+            "description": "Sector."
+          },
+          "totalUsd": {
+            "description": "Disclosed USD."
+          }
+        }
+      },
+      "type": "array"
+    },
+    "shortSignals": {
+      "description": "Scored sell-side signals; same fields as `longSignals`.",
+      "items": {},
+      "type": "array"
+    },
+    "shorts": {
+      "description": "Short signals."
+    },
+    "sources": {
+      "additionalProperties": true,
+      "description": "Per-source status — which filing feeds answered."
+    },
+    "stale": {
+      "description": "True when the snapshot is past its refresh interval."
+    }
+  },
+  "type": "object"
+}

AddedAug 17, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and idempotency profile is covered without the description. The description adds a useful ordering guarantee ('newest first') and the disclosure-based nature of the data, but says nothing about disclosure lag, pagination limits beyond the schema, or data source, so with annotations carrying most of the load a 3 is appropriate.

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?

A single front-loaded sentence with zero filler; the resource and its ordering constraint appear immediately. Nothing is repeated or 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?

An output schema exists, so return values need not be described, and annotations cover the safety profile, making this sufficient for a zero-required-parameter read tool. The one remaining gap is the meaning of 'recently disclosed' (how far back the data reaches or how large the disclosure lag is), which the agent may want in order to interpret results.

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% and the single 'limit' parameter is fully documented with its default and 1-25 range. The description adds no parameter detail beyond the schema, which matches the baseline of 3 when the schema does the heavy lifting.

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 names a specific resource (recently disclosed stock and asset transactions by US Congress members) and its ordering (newest first), which no sibling tool covers. It lacks an explicit action verb like 'list' or 'get', but the resource and scope are unambiguous enough to distinguish it from siblings like get_government_contracts or track_whales.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. 'Recently disclosed' implies a recency window but leaves the definition of 'recent' to inference, and nothing routes the agent between this and the 40+ other analytics tools.

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

All Agent Einstein — Crypto & Market Intelligence 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.