Skip to main content
Glama
ElectionData MCP

ElectionData MCP

swing

Read-only

Calculates vote-share change per seat for a coalition or party across two elections, with renamed seats listed separately.

Instructions

Vote share per seat for one coalition or party in two elections, and the change. Seats whose name changed are listed apart.

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_from": "<election_from>",
      "election_to": "<election_to>",
      "group": "<group>"
    },
    "name": "swing"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNocoalition
groupYes
stateNo
election_toYes
election_fromYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare the tool read-only and open-world, so safety is covered. The description adds useful behavioral context: it computes vote share and change per seat and notes that seats with changed names are handled separately. That adds value beyond the annotations, though it says nothing about result size or pagination.

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?

The definition is two sentences with no wasted words and the core operation is front-loaded. The special handling of renamed seats is included compactly.

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

Completeness3/5

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

For a read-only analytical tool with an output schema and annotations, the description covers the core calculation and the renamed-seat edge case. However, it omits usage guidance and any mention of the state filter, leaving meaningful gaps for an agent choosing among analytical siblings.

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?

With zero schema description coverage, the description must carry parameter meaning. It maps 'one coalition or party' to the group and by enum and 'two elections' to election_from/election_to, but it leaves the optional state filter and the by default unexplained.

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 computation: vote share per seat for one coalition or party across two elections, plus the change. It is clear enough to distinguish the core operation, but it never contrasts this tool with siblings such as compare or seat_history.

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?

The description implies the tool is for swing analysis between two elections, but it gives no explicit when-to-use guidance, no exclusions, and no alternatives. An agent must infer its role from the description alone.

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