Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Most Active Politicians

get_politicians_most_active
Read-only

Rank congressional traders by trade count over a chosen lookback period, returning tickers, buy/sell values, and top trades to identify prolific political traders.

Instructions

Discover the most active congressional traders ranked by trade count within a lookback period. Returns each politician with trade count, tickers traded, buy/sell values, and top tickers. Useful for identifying the most prolific political traders.

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_politicians_most_active"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default: 10, max: 50)
periodNoLookback period (default: '90d')

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: results are ordered by trade count, are constrained to a lookback window, and each row carries trade count, tickers, buy/sell values, and top tickers. It does not mention defaults (10/90d) or the cap of 50, but those live in the schema.

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?

Three short sentences, front-loaded with the core purpose and answer shape. The final sentence is largely redundant with 'most active'/'most prolific' framing already established, so one sentence could be trimmed, but there is no bulk or tangents.

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?

The tool is simple (2 optional parameters, no nested objects) and an output schema exists, so return values need not be spelled out in detail. The description covers purpose, ranking basis, and row shape, leaving only sibling differentiation and default values unaddressed, both of which are minor here.

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%, with both parameters documented including the enum values and the default/max for limit, so the schema does the heavy lifting. The description only alludes to 'lookback period' and adds no semantics about how trade count is computed within a period or how ties are ranked. Baseline 3 is appropriate.

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 ('Discover the most active congressional traders') plus the ranking key ('ranked by trade count') and the scoping dimension ('within a lookback period'). An agent can tell this is a ranked leaderboard, but the description never distinguishes it from close siblings such as get_politicians_pnl_leaderboard, get_policy_trade_leaderboard, or get_politician_activity.

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 closing sentence ('Useful for identifying the most prolific political traders') implies a use case but gives no explicit when-to-use versus when-to-prefer-a-sibling rule. There are at least three nearby leaderboard/activity tools in the sibling list and none are named as alternatives or exclusions.

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