Skip to main content
Glama

get_vote_details

Read-onlyIdempotent

Retrieve per-district Basel-Stadt results for a specific vote by title or date, covering Basel, Riehen, Bettingen, and abroad to compare local outcomes.

Instructions

Per-district Basel-Stadt results (Basel, Riehen, Bettingen, abroad) for one vote. Give vote_title and/or date

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_vote_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD
vote_titleNoPartial title, e.g. CO2-Gesetz

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / properties / date / description
      Previous value: -"Vote date in YYYY-MM-DD format (e.g. '2024-11-24')"New value: +"YYYY-MM-DD"
    • changedInput schema / properties / vote_title / description
      Previous value: -"Partial or full vote title to look up (e.g. 'CO2-Gesetz', 'AHV')"New value: +"Partial title, e.g. CO2-Gesetz"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact: results are broken down by district and limited to Basel-Stadt. It does not say what happens when a partial title matches multiple votes, or when a date has several ballots.

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 short sentences, the purpose first and the parameters second, with no filler. Slightly terse for the amount of behavioral information an agent might want, 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?

With no output schema, the description carries the burden of describing what comes back, and it never mentions the return shape (e.g. per-district yes/no shares, turnout) or the language of vote titles. For a two-parameter read tool this is workable but leaves real gaps an agent must discover by calling.

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 coverage is 100% and already documents both parameters, including the YYYY-MM-DD format and partial-title matching. The description only restates that both are optional and can be combined ('and/or'), which is a marginal addition over the schema's required: [] definition.

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 verb-and-resource: per-district vote results for Basel-Stadt (Basel, Riehen, Bettingen, abroad), which is a distinct granularity from siblings like get_voting_results and search_votes. It stops short of naming those siblings explicitly, so an agent must infer that this is the district-breakdown complement rather than the aggregate results tool.

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?

"Give vote_title and/or date" is invocation guidance for the lookup key, not when-to-use guidance. There is no statement of when this tool should be preferred over get_voting_results or search_votes, nor any exclusion such as 'only works for Basel-Stadt votes'. Usage is implied by the geographic scope rather than declared.

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

Deploy Server

Other Tools