Skip to main content
Glama
ElectionData MCP

ElectionData MCP

search

Read-only

Find exact seat names, candidate_uid, party_uid, or coalitions from loose text; call this first when a user names a seat, person, or party.

Instructions

Find exact seat names, candidate_uid, party_uid or coalitions from loose text. Call this first when the user names a seat, person or party.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
textYes
limitNo
stateNo

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 that it resolves loose text into canonical names and UIDs, which is useful behavior beyond the annotations, but says nothing about ambiguity, multiple matches, or how limit/state affect results.

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, front-loaded with the capability and followed by the routing rule. No redundant or filler wording.

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. Still, for a 4-parameter tool with zero schema coverage, the description leaves the geographic filter and result cap unexplained, which an agent needs to call it well.

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 carries the burden: it explains 'text' as loose text and implies the 'kind' dimension via seat/candidate/party. However, the 'state' and 'limit' parameters are entirely unaddressed, and 'coalitions' is mentioned despite not appearing in the kind enum.

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 ('Find') and specific resources ('exact seat names, candidate_uid, party_uid or coalitions') plus the input mode ('from loose text'). This clearly marks it as a fuzzy name/ID resolver rather than a dataset or geography lookup, though it doesn't explicitly distinguish itself from siblings like find_seat_by_location or search_datasets.

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?

'Call this first when the user names a seat, person or party' gives a clear triggering condition and positions the tool as the entry point in a workflow. It stops short of stating when not to use it or naming the alternative for location-based or dataset lookups.

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