Skip to main content
Glama
ElectionData MCP

ElectionData MCP

seat_lineage

Read-only

Trace a Malaysian election seat’s historical results through boundary changes and view notes for each change from the ElectionData.MY API.

Instructions

A seat's results back through boundary changes, with notes on each change (from the ElectionData.MY API).

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

Input Schema

NameRequiredDescriptionDefault
seatYes
stateNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 safe external-read profile is covered structurally. The description adds that each boundary change carries notes, which is useful behavioral context, but says nothing about depth of lineage, pagination, or what happens when a seat has no boundary changes.

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?

A single compact sentence with no wasted words, front-loading the core concept. It is efficient, though its brevity borders on under-specification rather than crispness.

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?

An output schema exists, so return values needn't be spelled out, but the combination of a 0%-coverage parameter schema and zero usage guidance leaves the agent without enough to call this correctly versus seat_history. The description should do more given that gap.

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 bears the full burden of explaining parameters and does not: it never says that 'seat' is the required lookup key or what 'state' disambiguates or why it defaults to null. Both parameters are effectively undocumented.

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

Purpose3/5

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

The description indicates a specific resource — a seat's electoral results traced back through boundary changes, with per-change notes — but the verb/action is left implicit ('A seat's results back through...'), and it never distinguishes itself from the sibling seat_history, which reads as near-synonymous. An agent can guess the domain but not confidently the distinct output.

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 preconditions, and no mention of alternatives such as seat_history, despite that sibling being an obvious candidate for confusion. The parenthetical '(from the ElectionData.MY API)' is provenance, not usage guidance.

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