Skip to main content
Glama

Federal vote results

get_voting_results
Read-only

Retrieve official Swiss federal popular-vote results for a vote day (default: most recent), including national yes-share, turnout, acceptance, cantonal majority, and optional per-canton breakdown.

Instructions

Official results of federal popular votes for a vote day (default: most recent): national yes-share, turnout, accepted/rejected, cantonal majority, and optional per-canton breakdown.

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
dateNoVote day YYYY-MM-DD (see list_vote_dates); default: most recent
languageNoLanguage for proposal titlesen
include_cantonsNoInclude per-canton results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety behavior is covered. The description adds useful context by saying results are official, default to the most recent vote day, and can include optional per-canton breakdowns. It does not cover rate limits or response structure, but that is a minor gap for this read-only tool.

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 dense sentence that front-loads the core purpose and enumerates the returned fields. Every clause contributes to identifying the operation or its output. There is no redundant wording.

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 read-only tool with three optional, fully documented parameters and no output schema, the description is nearly complete. It lists the national result fields and the optional cantonal breakdown, which gives an agent a good sense of what will be returned. It could be slightly richer about response shape, but no critical invocation information is missing.

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%, so all three parameters are already documented in the schema. The description reinforces the date default and optional canton breakdown, but adds no syntax or format details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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: official results of federal popular votes for a vote day. It also enumerates the main result fields, making the tool clearly identifiable. It does not explicitly differentiate itself from the related list_vote_dates sibling, so it falls short of a 5.

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 description gives clear context that the tool is for a vote day and defaults to the most recent date. However, it does not say when to use this tool versus list_vote_dates or any other alternative, nor does it state exclusions. The guidance is implied rather than explicit.

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