Skip to main content
Glama
ElectionData MCP

ElectionData MCP

election_summary

Read-only

Retrieve seats won and votes by coalition and party, turnout, and uncontested seats for one Malaysian federal or state election, with optional state filtering.

Instructions

Seats won and votes by coalition and party, turnout and uncontested seats for one election. GE-xx = Malaysia unless a state is given; SE-xx = one block per state.

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>"
    },
    "name": "election_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
electionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 known. The description adds scope information (one election, coalition/party breakdown, turnout, uncontested seats) but says nothing about data source limits, coverage, or edge cases; an output schema exists, so return-format detail is not required.

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?

Two sentences, both front-loaded with the highest-value information (what is returned, then how to encode the election argument). The code-convention sentence is terse to the point of being cryptic, but nothing is wasted.

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?

For a two-parameter query tool with an output schema, the definition covers the return content and the election code convention. It still leaves gaps around valid code formats and how the state argument interacts with SE-style elections, which matters given 0% schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load, and it does explain the election code convention (GE-xx = national Malaysia, SE-xx = per-state blocks) and the role of state. It falls short of stating the exact code format or what state does when the election is already a state election, leaving some ambiguity.

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?

"Seats won and votes by coalition and party, turnout and uncontested seats for one election" names the concrete data the tool returns and its scope (a single election). It implicitly separates the tool from siblings like contest_result or byelections, but never explicitly says how it differs from them.

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: the tool summarizes one election, and the GE/SE code note hints at valid inputs. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for related questions (swing, contest_result, byelections).

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