Skip to main content
Glama

get_voting_results

Read-onlyIdempotent

Fetch national and cantonal popular vote results counted in Basel-Stadt since 2021, with optional year filter and result limit.

Instructions

Popular vote (Volksabstimmung) results as counted in Basel-Stadt: national and cantonal votes since 2021

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_voting_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoe.g. 2024 (omit for most recent)
limitNomax 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of votes to return (default: 10, max: 50)."New value: +"max 50"
    • changedInput schema / properties / year / description
      Previous value: -"Filter by year (e.g. 2024). If omitted, returns most recent votes."New value: +"e.g. 2024 (omit for most recent)"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful scope details about Basel-Stadt and national/cantonal votes since 2021, but it does not explain result structure, pagination, or what 'counted' means beyond the annotations.

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?

The description is a single front-loaded sentence with no redundant wording. It communicates the resource and scope efficiently.

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?

For a simple read-only tool with two optional, fully documented parameters and rich safety annotations, the description provides enough scope to call it correctly. The main minor gap is routing guidance relative to the other vote-related tools.

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 100%, so the year and limit parameters are already fully documented in the schema. The description does not add further meaning, constraints, or format guidance beyond the structured field documentation.

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 names a specific resource (popular vote results), a geographic scope (Basel-Stadt), and a temporal scope (since 2021), so an agent can tell broadly what data it returns. However, it does not explicitly distinguish this tool from siblings such as search_votes or get_vote_details.

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?

The Basel-Stadt and since-2021 scope implies when the tool is appropriate, but there is no explicit when-to-use guidance, no exclusions, and no comparison with the vote-related sibling tools.

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