Skip to main content
Glama
ElectionData MCP

ElectionData MCP

seat_features

Read-only

Retrieve one row per election seat with turnout, majority, winner, coalition vote share, prior result, and demographics for modelling.

Instructions

One row per seat for an election: turnout, majority, winner, vote share per coalition, previous result and voter demographics. Ready for modelling.

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": "seat_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoparlimen
stateNo
electionYes

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the unit of return (one row per seat) and the election scoping, but says nothing about volume (how many seats per election), whether results span multiple elections, or whether a missing state means national scope.

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?

Two tight sentences, front-loaded with the most decision-relevant fact (one row per seat per election). The trailing 'Ready for modelling' is filler but costs little.

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?

An output schema exists, so return values need not be spelled out, and annotations cover read-only behavior. However, for a tool with three parameters at 0% schema coverage, the description leaves the level/state filtering semantics entirely unexplained, which is the main remaining gap.

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%, so the description must carry parameter meaning and it does not. 'For an election' loosely maps to the required `election` parameter, but `level` (parlimen vs dun) and `state` (nullable, defaulting to null) are never explained — an agent cannot tell that null state means all states or that level controls parliamentary vs state-assembly seats.

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 names a concrete resource and granularity ('one row per seat for an election') and enumerates the payload (turnout, majority, winner, coalition vote share, prior result, demographics), which distinguishes it from narrower siblings like seat_demographics or seat_history. It lacks an explicit verb, so the agent must infer that this is a retrieval tool, but the content is specific enough to select on.

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?

'Ready for modelling' is the only usage hint and is too vague to route between this and seat_demographics, seat_history, contest_result or swing. There is no statement of when to prefer this composite table over those alternatives, and no prerequisites or exclusions.

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