Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Politician Votes

get_politician_votes
Read-only

Retrieve a politician’s congressional voting records by slug, including bills, Yea/Nay/Not Voting positions, and outcomes to assess alignment with their trading activity.

Instructions

Get voting records for a politician by slug. Returns congressional votes with bill info, position (Yea/Nay/Not Voting), and result. Useful for assessing alignment between a politician's votes and their trading positions. Requires Bioguide ID resolution.

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

Input Schema

NameRequiredDescriptionDefault
slugYesPolitician URL slug (e.g., "sen-nancy-pelosi")
limitNoMaximum results to return (default: 10, max: 100)
offsetNoPagination offset (default: 0)

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the description only needs to add operational context. It does add the shape of the result (bill info, Yea/Nay/Not Voting position) and notes that slug is internally resolved to a Bioguide ID, which is useful but phrased ambiguously — it could read as an input requirement rather than internal handling.

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 action and return contents, and no filler. The trailing 'Requires Bioguide ID resolution' sentence is the weakest link because it is vague rather than wasteful.

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?

With annotations, a fully documented schema, and an output schema, the description only needs to explain purpose and result shape, which it does. The remaining gap is sibling routing: it does not tell the agent how this differs from the other congressional-vote and politician-activity tools in the same family.

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 coverage is 100% with descriptions for slug, limit, and offset including defaults, ranges, and an example. The description only restates that lookup is by slug and says nothing about limit/offset behavior, so the baseline 3 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 voting records for a politician by slug') and scopes it to an individual politician rather than votes in general, which implicitly separates it from the sibling get_recent_congressional_votes. It does not name that sibling explicitly, so the differentiation is inferential rather than stated.

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?

Offers one concrete use case ('assessing alignment between a politician's votes and their trading positions'), which implies context for calling it. However, it gives no when-not guidance and never mentions when an agent should prefer get_recent_congressional_votes, get_politician_transactions, or get_politician_activity instead.

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