Skip to main content
Glama
ElectionData MCP

ElectionData MCP

polling_centre_results

Read-only

Retrieve votes per polling stream or polling district for a given seat and election, covering GE-12 to GE-15 and many state elections.

Instructions

Votes per polling stream (saluran) or polling district (dm) for one seat and election. Available for GE-12 to GE-15 and many state elections.

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

Input Schema

NameRequiredDescriptionDefault
seatYes
levelNosaluran
stateNo
electionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 a real behavioral constraint the annotations do not: the electoral dataset only covers GE-12 through GE-15 plus many state elections, so an agent knows requests outside that range will fail or return nothing. It does not say what happens for unsupported elections or how missing polling districts are handled.

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?

Two sentences, zero filler: the resource and grain are front-loaded, then the coverage caveat. Every clause carries information an agent cannot get from the schema.

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

Completeness4/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, and the description covers purpose, grain, and dataset coverage. The remaining gap is the undocumented 'state' parameter, but for a four-parameter read-only tool this is close to sufficient.

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 carries real weight and does decode the otherwise opaque 'saluran' and 'dm' jargon for the level enum, and clarifies that seat and election are single values. However, it says nothing about the 'state' parameter or what format an election identifier takes, leaving half the parameters undocumented in both schema and description.

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 with its granularity ('Votes per polling stream (saluran) or polling district (dm)') and the scoping keys ('for one seat and election'), which is enough for an agent to distinguish a granular vote breakdown from aggregate tools like contest_result or election_summary. It falls short of a 5 because it never explicitly contrasts itself with those siblings.

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 by the level-of-granularity framing; there is no explicit 'use this when you need X rather than Y' guidance. The availability clause ('GE-12 to GE-15 and many state elections') is genuinely useful context for deciding whether the tool can serve a request at all, which lifts it above a bare 2.

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