Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Politician Activity

get_politician_activity
Read-only

Analyze a politician's trading patterns by retrieving period-based activity metrics—30-day, 90-day, yearly, or all-time—with buy/sell counts, values, top tickers, and transaction breakdown.

Instructions

Get activity metrics for a politician broken down by period (30d, 90d, 1y, all-time). Includes buy/sell counts and values per period, most traded tickers (top 10), and transaction type breakdown. Useful for analyzing trading patterns over time.

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": {
      "slug": "<slug>"
    },
    "name": "get_politician_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPolitician URL slug (e.g., "sen-nancy-pelosi")

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: the fixed period set (30d, 90d, 1y, all-time), per-period buy/sell counts and values, top-10 ticker concentration, and transaction-type breakdown — none of which is derivable from the one-parameter schema.

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?

Three short sentences, zero filler: what it returns first, the aggregation periods and response contents second, the analytical use case last. No redundant restatement of the title or annotations.

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?

For a single-parameter read tool with an output schema and full annotation coverage, this is close to complete — the description even pre-summarizes the output shape and period buckets. The one remaining gap is routing guidance against the many related politician tools in the sibling list.

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?

The only parameter is 'slug' and the schema documents it at 100% coverage with an example, so the schema carries the semantics. The description never mentions the slug or its expected format, so it adds nothing on this dimension — the baseline 3 for high schema coverage applies.

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 ('Get activity metrics for a politician') plus the aggregation axis ('broken down by period'), which implicitly separates it from raw-transaction siblings like get_politician_transactions. However, it never names which sibling to use instead for granular trades, recent trades, or scorecards, so the differentiation is inferential rather than explicit.

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?

'Useful for analyzing trading patterns over time' implies a use case but gives no explicit when-to-use/when-not-to-use rules and no alternative routing. An agent must infer that this is the aggregate-summary tool rather than the transaction-listing tool.

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