Skip to main content
Glama
ElectionData MCP

ElectionData MCP

find_dashboard

Read-only

Retrieve English and Bahasa Malaysia dashboard links for Malaysian election seats, candidates, parties, coalitions, elections, or boundary maps by specifying the item type and name.

Instructions

Links to electiondata.my dashboard pages (English and Bahasa Malaysia) for a seat, candidate, party, coalition, election or boundary map.

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": {
      "kind": "<kind>",
      "text": "<text>"
    },
    "name": "find_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
textYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds modest value by noting results are dashboard links offered in both English and Bahasa Malaysia, but it says nothing about matching semantics (exact vs fuzzy name), ambiguity handling, or what happens when no dashboard exists.

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?

One dense sentence with no filler, and the resource is front-loaded before the enumeration of kinds. Nothing is repeated or 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?

An output schema exists, so return values need not be described, and the two-parameter surface is small. Still, for a lookup tool whose usefulness depends on name matching, the absence of any guidance on the 'text' input or on failed/ambiguous lookups leaves a real gap.

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 does decode the enum usefully — 'boundary map' maps to the otherwise opaque 'redelineation' value — but the required 'text' parameter is never explained (name spelling, aliases, whether partial matches work), leaving the primary input undocumented in both schema and description.

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?

States a specific resource (electiondata.my dashboard page links) and enumerates the six subject types it covers, so an agent can tell it apart from data-returning siblings like search or run_sql. The verb 'Links to' is weak but the outcome is unambiguous.

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: 'find' plus the list of kinds suggests 'use when you want a dashboard URL rather than data', but no sibling (search, candidate_profile, seat_history) is named and no when-not condition is given. An agent must infer the choice from sibling names alone.

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