Skip to main content
Glama
ElectionData MCP

ElectionData MCP

party_history

Read-only

Retrieve a party’s or coalition’s seats and votes over time in a selected Malaysian state, with historical name changes merged for consistent comparisons.

Instructions

A party's or coalition's seats and votes over time in one state, with old names merged (e.g. PERIKATAN into BN).

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": {
      "party": "<party>"
    },
    "name": "party_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
partyYes
stateNoMalaysia
election_typeNoparlimen

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 already declare readOnlyHint and openWorldHint, so the description's main added value is the historical name-merging behavior (e.g. PERIKATAN into BN), which materially changes how an agent should interpret results. It stops short of describing coverage limits, time range, or how merged series are ordered.

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?

A single front-loaded sentence with the resource, scope, and a concrete normalization example; no filler and nothing buried.

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 explained, but for a three-parameter tool with zero schema coverage the definition should still cover the election_type choice and the state default. As written it is adequate but leaves those gaps for the agent to guess.

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 the load; it clarifies that party accepts coalitions and historical aliases and that state scopes results to a single state. It says nothing about election_type (parlimen vs dun) or what the 'Malaysia' default means, leaving one of three parameters undocumented.

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 (a party's or coalition's seats and votes) and scope (over time, one state), so the agent knows exactly what data comes back. It does not distinguish itself from the similarly named sibling seat_history, leaving the party-level vs seat-level split to inference.

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 scope wording ('over time', 'in one state') rather than stated: there is no explicit 'use this when tracking party trends across elections' and no named alternative such as seat_history or swing. An agent can infer the intent, but nothing routes it away from a wrong sibling.

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