Signal8

Get Senate Trades by Ticker

get_senate_trades_by_ticker

Read-only

Reverse lookup: which politicians recently traded a given ticker. Returns recent STOCK Act disclosures for that symbol with politician info, transaction type, and amount.

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": "get_senate_trades_by_ticker"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return (default: 50, max: 100)
`offset`	No	Pagination offset (default: 0)
`ticker`	Yes	Stock ticker symbol (e.g., "AAPL", "NVDA")

Output Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJun 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results to return (default: 50, max: 100)"
```
- addedInput schema / properties / offset / description
```
Added value: +"Pagination offset (default: 0)"
```
- addedInput schema / properties / ticker / description
```
Added value: +"Stock ticker symbol (e.g., \"AAPL\", \"NVDA\")"
```
- removedOutput schema / required
```
Removed value: -[
-  "data"
-]
```

Changed1 schema field changedJun 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {}
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedJun 27, 2026

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, non-destructive, closed-world), and the description adds real context beyond them: the data source (STOCK Act disclosures), the recency scoping ('recently'), and the shape of each record (politician info, transaction type, amount). It stops short of stating the actual lookback window used for 'recent', which is the one behavioral detail an agent might need.

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 sentences, zero filler, with the reverse-lookup framing front-loaded before the return contents. Nothing could be removed without losing information.

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 annotations, a full schema, and an output schema, the definition covers everything needed to invoke the tool correctly. The remaining gap is the unquantified 'recent' window, which matters for interpreting results but not for calling the tool.

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 coverage is 100%, with ticker, limit, and offset all documented in the schema itself, so the baseline is 3. The description adds only the framing that ticker is the pivot of the lookup and says nothing about pagination or result limits beyond what the schema already provides.

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 verb and resource — a ticker-first ('reverse lookup') listing of recent STOCK Act trades with politician, transaction type, and amount. That framing implicitly distinguishes it from politician-first siblings like get_politician_recent_trades, but it never names those alternatives explicitly.

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?

'Reverse lookup' implies the ticker-first use case, so an agent can infer that this is the tool to reach for when starting from a symbol rather than a person. However, there is no explicit when-to-use/when-not statement and no named alternative for the politician-first path.

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

All Signal8 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.