Skip to main content
Glama
ElectionData MCP

ElectionData MCP

seat_demographics

Read-only

Retrieve voter demographics for a seat from an election's voter roll, broken down by sex, age band, ethnicity and voter type. Specify state or election optionally.

Instructions

Voters in a seat by sex, age band, ethnicity and voter type, from the voter roll of an election (latest if not given).

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

Input Schema

NameRequiredDescriptionDefault
seatYes
stateNo
electionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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, covering the safety and external-data profile. The description adds useful context about the voter-roll source and defaulting to the latest election, but does not disclose permissions, rate limits, or how ambiguous seat/state combinations 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler, and the demographic breakdowns are packed efficiently. Slightly more structure could separate the core purpose from the election default, but it is not verbose.

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

Completeness2/5

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

For a three-parameter demographic query with no schema parameter descriptions, the definition leaves the state parameter entirely unexplained and does not specify seat/election formats or ambiguity handling. The output schema and annotations reduce the burden for return values and safety, but input semantics remain materially incomplete.

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. It clarifies seat and election, including the latest-election default, but never mentions the state parameter or explains seat/election formats or the seat-state relationship.

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 resource—voter demographics for a seat—and names the breakdown dimensions: sex, age band, ethnicity and voter type. It also gives the data source and election default, though it does not explicitly distinguish itself from siblings such as compare or seat_features.

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?

There is no when-to-use guidance, no exclusions, and no alternatives named. The only usage-like detail is that the latest election is used when election is omitted, which is parameter behavior rather than tool-selection guidance.

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