Skip to main content
Glama
ElectionData MCP

ElectionData MCP

marginal_seats

Read-only

Find the closest election contests ranked by smallest majority, showing winner and runner-up. Filter results by election, state, or maximum majority to identify competitive seats.

Instructions

Closest contests in an election, smallest majority first, with winner and runner-up.

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": {
      "election": "<election>"
    },
    "name": "marginal_seats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNo
electionYes
max_majorityNo
max_majority_percNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine value with the sort order ('smallest majority first') and the returned content ('winner and runner-up'), but says nothing about pagination, default result count, or how the majority filters narrow results — the filter behavior is the most consequential unknown for a ranked list.

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?

A single dense sentence with the sorting rule and output content front-loaded, and no wasted words. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, but with five parameters at 0% schema coverage and no usage guidance the definition is thin for the tool's complexity. In particular the two overlapping majority-threshold parameters are left entirely ambiguous, which is the main risk in invoking this correctly.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description bears the full explanatory burden and largely fails it. It implies the election parameter and hints that majority matters, but never explains state filtering, the limit, or the critical distinction between max_majority (absolute votes) and max_majority_perc (percentage) — an agent could easily confuse the two.

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?

The description states a specific resource and behavior: 'closest contests in an election, smallest majority first, with winner and runner-up.' This tells an agent it is a ranked list of competitive seats rather than a raw result lookup, which differentiates it informally from siblings like contest_result or election_summary. It stops short of naming an alternative outright, so it is not a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as contest_result for individual results or swing for change analysis. The agent must infer that this tool is for identifying tight races, and nothing tells it when a different tool would be better.

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