Skip to main content
Glama
ElectionData MCP

ElectionData MCP

contest_result

Read-only

Fetch full results for one election contest by election and seat, including each candidate's votes and share, outcome, turnout, rejected votes, and majority.

Instructions

Full result of one contest: every candidate's votes, share and result, plus contest stats (voters, turnout, rejected votes, majority).

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>",
      "seat": "<seat>"
    },
    "name": "contest_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
seatYes
stateNo
electionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 useful content about what the payload contains (per-candidate votes and shares, plus voters, turnout, rejected votes, majority), but says nothing about data sourcing, freshness, or failure behavior when a seat/election combination doesn't exist.

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 front-loaded sentence that enumerates the returned contents without padding. Every clause (candidate results, then contest stats) carries information, and nothing is repeated from the title or schema.

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 explained in prose, and the annotations cover the read-only profile. The gap is on the input side: with four undocumented parameters and no guidance on required versus optional identifiers, the definition leaves an agent short of what it needs to construct a correct call.

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 four parameters, so the description must carry the meaning. It only implies that 'election' and 'seat' identify the contest; the optional 'date' and 'state' parameters are never mentioned, and the agent is left to guess whether they disambiguate multi-year or multi-state contests.

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 specific resource and scope: the full result of ONE contest, listing candidate-level votes/share/result plus aggregate contest stats. That is concrete enough to distinguish it from aggregate siblings like election_summary or historical tools like seat_history. It stops short of explicitly naming a sibling to disambiguate against.

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?

Usage is only implied: an agent can infer this is the tool for a single contest's detailed breakdown. There is no statement of when to prefer it over election_summary, seat_history, or polling_centre_results, and no preconditions such as needing a known seat name.

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