Skip to main content
Glama
ElectionData MCP

ElectionData MCP

candidate_profile

Read-only

Fetch a candidate's contest history with party at the time, result, and totals; use search to get candidate_uid first.

Instructions

Every contest a candidate stood in, with party at the time and result, plus totals. Get candidate_uid from search.

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": {
      "candidate_uid": "<candidate_uid>"
    },
    "name": "candidate_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidate_uidYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 externally. The description adds the useful domain detail that party is recorded 'at the time' of each contest, but says nothing about coverage limits, ordering, or performance for candidates with very long histories.

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?

Two short sentences with zero filler: the first front-loads what is returned, the second front-loads the prerequisite. Nothing is redundant with the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value detail needn't be spelled out, and a single required identifier is fully explained along with where to source it. For a read-only, one-parameter lookup, nothing an agent needs to invoke it correctly is missing.

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 description coverage is 0% for the single candidate_uid parameter, so the description must carry the meaning — and it does, identifying it as a candidate UID obtained from the search tool rather than a name or free-text query. It could still be more explicit that a name string will not work, but the origin guidance is substantive.

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 states a specific resource and scope: every contest a candidate stood in, with party-at-time, result, and totals. That is enough to distinguish it from aggregate tools like election_summary or swing, though 'plus totals' is left undefined and the sibling differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly establishes the prerequisite path ('Get candidate_uid from search'), which routes the agent to the correct sibling before calling this tool. It stops short of stating when-not to use it or what to do if a candidate has no recorded contests.

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