Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Most Active Politicians

get_politicians_most_active
Read-only

Identify the most active congressional traders by trade count within a chosen period. Rank politicians with trade metrics and top tickers to uncover prolific political trading activity.

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.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds specifics on return fields (trade count, tickers, buy/sell values) and behavior (ranking by trade count, lookback period). 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with key information. No wasted words.

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?

Tool has only 2 parameters, description fully explains purpose and returned data. Output schema exists to detail exact return fields; no gaps.

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%. Description mentions lookback period and default but does not add meaningful extra context beyond what the schema already provides.

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?

Description clearly states verb 'discover' and resource 'congressional traders ranked by trade count within a lookback period'. It is specific and distinguishes from other politician tools like get_politician_activity which focuses on individual 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?

Implies usage for identifying prolific traders but lacks explicit guidance on when to use versus alternatives. No exclusions or when-not conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/signal8ai/signal8-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server