Skip to main content
Glama
ElectionData MCP

ElectionData MCP

seat_history

Read-only

Retrieve every election contest for a Malaysian seat, newest first, including winner, party, coalition, majority, and turnout; use seat name to track results as codes change.

Instructions

Every contest held in a seat, newest first: winner, party, coalition, majority, turnout. Seat codes change over time; the history follows the seat name.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
seatYes
stateNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare this is a read-only, open-world lookup, so the safety bar is low; the description still adds real behavior: results are ordered newest first, and lookups resolve by seat name rather than code, which matters because codes change. It does not address pagination or result-size limits, which is the main remaining gap.

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 compact sentences, the primary purpose front-loaded and the identifier caveat immediately after. Every clause carries information an agent needs.

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-value structure need not be explained, yet the description still summarizes the key fields. For a simple two-parameter read tool it is nearly complete; only the silent 'state' parameter keeps it below full marks.

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 the burden. It usefully clarifies that 'seat' should be a seat name that survives code changes, but says nothing at all about the optional 'state' parameter, leaving one of two inputs undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource: it lists every contest held in a given seat, newest first, and names the returned dimensions (winner, party, coalition, majority, turnout). The clause about seat codes changing and history following the seat name separates it from code-keyed lookups and from party_history-style 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 implied rather than stated: an agent can infer this is the tool for per-seat electoral history, and the seat-code caveat tells it what identifier to expect. There is no explicit when-not-to-use guidance or named alternative (e.g. seat_lineage or byelections) to route between.

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