Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Policy-Trade Leaderboard

get_policy_trade_leaderboard
Read-only

Ranks politicians by trades near executive-order signings in affected sectors, helping researchers spot policy-adjacent trading patterns. Sector matches are broad starting points, not evidence.

Instructions

Rank politicians (Congress + executive branch) by trades that occurred near executive-order signings in sectors the orders affect, i.e. who trades most around policy activity. Each row includes the politician, flaggedTradeCount, totalEstimatedUsd, topSector, and an exampleEvent. Defaults to the "traded 1-14 days before signing" lens; same-day trades are always excluded. Matches are sector-level co-occurrence: the official traded a stock in a sector the executive order affects, within a window of its signing date. Sector matches are broad and many trades coincide with policy activity by chance; a match is a starting point for research, not evidence of foreknowledge. The matchBasis field describes match strength only ('sector' = broad sector match), not culpability, and matchCount is how many EOs matched in the window (a noise indicator).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_policy_trade_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoRanking order: 'usd' (default, estimated USD value) or 'count' (flagged-trade count)
limitNoMaximum results to return (default: 50, max: 100)
offsetNoPagination offset (default: 0)
windowNoMatch window in days around the EO signing date (default: 14, max: 30)
directionNoWhich side of the signing date to include: 'before' (default), 'after', or 'both'

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • changedInput schema / properties / sort / description
      Previous value: -"Ranking order: 'usd' (default — estimated USD value) or 'count' (flagged-trade count)"New value: +"Ranking order: 'usd' (default, estimated USD value) or 'count' (flagged-trade count)"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior5/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 substantial context beyond them: the default window/direction behavior, the hard exclusion of same-day trades, the sector-level co-occurrence matching rule, and how to interpret matchBasis and matchCount. It also warns that matches are broad and often coincidental, which is exactly the behavioral caveat an agent needs before presenting results.

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?

The core operation is front-loaded in the first sentence, followed by output fields and then interpretation caveats in a sensible order. There is mild redundancy — 'i.e. who trades most around policy activity' restates the opening, and the sector co-occurrence rule is explained twice — but nothing is seriously out of place.

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?

For a zero-required-parameter, read-only leaderboard tool with a full output schema and complete schema descriptions, the description covers scope, defaults, exclusions, and interpretation. An agent could call and correctly frame the results without additional context.

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 every parameter is already documented at the field level; the description adds only a prose restatement of the combined default ('1-14 days before signing') rather than new syntax or constraints. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb and resource ('Rank politicians ... by trades that occurred near executive-order signings') and clarifies the ranking semantics with 'who trades most around policy activity'. It is clear enough to distinguish from generic politician tools, but it never names the closest sibling (get_policy_trade_overlap), leaving that differentiation to inference.

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?

The description establishes the default lens ('traded 1-14 days before signing', same-day trades always excluded) and how to read the output, which implicitly defines the intended use case. However, it gives no explicit when-to-use/when-not guidance relative to alternatives such as get_policy_trade_overlap or get_politician_recent_trades.

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

Deploy Server

Other Tools