Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Policy-Trade Overlap

get_policy_trade_overlap
Read-only

Identify trades by a politician that coincide with executive orders affecting the traded sector. Shows trade dates relative to EO signing, with sector-level match strength and count of matched EOs.

Instructions

For a single politician, list trades that occurred within a window of days before or after the signing of an executive order affecting the traded sector. Each row contains the trade, the nearestEvent, daysDelta (negative = traded N days before EO signing, positive = traded N days after), matchBasis, and matchCount, plus a summary (totalFlags, totalEstimatedUsd, topSector). Defaults to trades 1-14 days BEFORE signing; same-day trades are always excluded (intraday ordering is unknowable). Unlike get_donor_trade_overlap, executive-branch (exec-) slugs return REAL data here: both congressional and executive trade sources feed the overlap computation. IMPORTANT: 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 will 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), never culpability, and matchCount shows how many EOs matched in the window (a noise indicator).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesPolitician URL slug — congressional ("sen-nancy-pelosi", "rep-...") or executive branch ("exec-...")
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

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description consistently describes a read-only operation. It exceeds annotation value by detailing exclusions (same-day trades), default direction, and match interpretation (sector-level, not culpability). No contradictions.

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?

Description is well-organized with a clear lead sentence followed by details on output, defaults, caveats, and comparison. It is slightly long but each sentence adds value given the tool's complexity. Could be tightened slightly without losing clarity.

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?

Given the tool's complexity (5 parameters, sector-level matching nuance), the description covers defaults, exclusions, match interpretation, and distinction from a sibling. Output schema exists, so return value details are offloaded. The warning about false positives completes the picture for appropriate use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant meaning: explains slug formats (congressional vs exec), defaults for window and direction, and clarifies that same-day trades are excluded. It also elaborates on output fields like matchBasis and matchCount beyond schema hints.

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 clearly states the tool lists trades for a single politician within a window around executive order signing, with specific verb 'list' and resource 'trades'. It distinctly separates from sibling get_donor_trade_overlap by noting executive-branch slug behavior.

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

Usage Guidelines4/5

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

Provides clear context: it's for a single politician, defaults to 1-14 days before, and warns that matches are sector-level and not evidence. It could be improved by explicitly stating when not to use or listing alternatives, but the sibling context and differentiation from get_donor_trade_overlap offer adequate guidance.

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