Skip to main content
Glama
ElectionData MCP

ElectionData MCP

live_turnout

Read-only

Retrieve provisional polling-day turnout from the SPR feed every five minutes (08:00–18:00 MYT) for a given election, with optional level, time-slot, or seat filters.

Instructions

PROVISIONAL live turnout on polling day (SPR feed, every 5 minutes, 08:00-18:00 MYT). election like 'mlk-se16'. Optional level, HHMM slot, or seat filter.

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

Input Schema

NameRequiredDescriptionDefault
seatNo
timeNo
levelNo
electionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint. The description adds genuinely useful behavioral context beyond them: the data is provisional, sourced from the SPR feed, refreshed every 5 minutes, and bounded to 08:00-18:00 MYT. It stops short of stating what happens outside that window or whether a missing slot returns empty.

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?

Three short clauses, front-loaded with the most decision-relevant fact (PROVISIONAL, live, polling day). No filler, and the refresh cadence and time window are packed into the opening sentence.

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 described. For a 4-parameter tool with zero schema coverage, though, the description should explain the level enum values and the seat identifier format, which it does not.

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 description coverage is 0%, so the description must carry parameter meaning. It does add real value for two parameters — the election ID format ('mlk-se16') and the HHMM time format — but leaves 'seat' without a format example and the level enum values (parlimen/dun/dm) 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?

States a specific resource (live turnout) with strong qualifiers: 'PROVISIONAL', 'on polling day', and the SPR feed source. That distinguishes it from historical-result siblings like contest_result or election_summary, but no sibling is named explicitly, so the differentiation is inferred 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?

The implicit when-to-use is clear from 'on polling day ... 08:00-18:00 MYT' — this tool is only meaningful during that window. However, there is no explicit statement of when to use an alternative (e.g. final results after polling) and no prerequisites or exclusion guidance.

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