Skip to main content
Glama
ElectionData MCP

ElectionData MCP

compare

Read-only

Evaluate 2–5 candidates, parties, or coalitions side by side across elections to identify differences in results and performance.

Instructions

Compare 2 to 5 candidates (by candidate_uid), parties or coalitions (by acronym or uid) side by side across elections.

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

Input Schema

NameRequiredDescriptionDefault
idsYes
kindYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.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 safety profile is covered. The description adds one genuine behavioral constraint not present in the schema: the 2-to-5 element limit on ids. It does not describe scope limits, e.g. whether all ids must share the same kind or whether missing elections produce partial rows.

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 no filler; the entity list and identifier forms are packed into the same clause as the verb. Nothing could be removed without losing information.

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 values need not be explained. With only two parameters, the description covers cardinality, identifier syntax, and entity scope adequately. The one unresolved question for an agent is mixed-kind behavior, which is a minor gap.

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 parameters, and it does: it names candidate_uid for candidates, acronym or uid for parties/coalitions, and the 2-5 array size for ids. 'kind' is only implied by the enumeration of entity types rather than called out as the selector parameter, which keeps it from a 5.

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 verb (compare) and the exact resources (candidates, parties, coalitions) plus the comparison axis ('side by side across elections'). No sibling in the catalog performs a comparison, so the tool is distinguishable even without an explicit contrast. Slightly short of 5 because it does not say what the comparison yields.

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?

Gives an implied usage rule through the cardinality bound ('2 to 5') and the identifier forms, which tells the agent when the tool is applicable. It offers no explicit when-not guidance or pointer to alternatives such as search or candidate_profile for single-entity lookups.

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