Skip to main content
Glama

get_parliament_votes

Read-onlyIdempotent

Retrieve recorded parliamentary votes for a specific affair using its OpenParlData affair ID. Use it to inspect how members voted on Swiss parliament business.

Instructions

Recorded votes on a parliamentary affair (Geschäft)

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": {
      "affair_id": "<affair_id>"
    },
    "name": "get_parliament_votes"
  }
}

Input Schema

NameRequiredDescriptionDefault
affair_idYesOpenParlData affair ID (from search_parliament_business)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / affair_id / description
      Previous value: -"OpenParlData affair ID (get from search_parliament_business results)"New value: +"OpenParlData affair ID (from search_parliament_business)"
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what a vote record contains, whether results are paginated, or how an affair with many votes is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is certainly concise, one fragment with no filler. But the brevity comes at the cost of under-specification — a verb-led clause stating what is returned would cost one more sentence and remove ambiguity.

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?

For a one-parameter read-only lookup with full schema coverage and no output schema, the description is minimally adequate. It still leaves unclear what shape the vote data takes (counts, parties, individual member votes), which matters for a parliamentary-votes tool.

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% and the single affair_id parameter is fully documented, including where to source it. The description adds no meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase names a specific resource (recorded votes) and scope (a single parliamentary affair, glossed as Geschäft), so the object of the call is inferable. However it is a bare noun phrase with no verb, and it does not distinguish itself from voting-adjacent siblings such as get_vote_details, search_votes, or get_voting_results.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any sibling alternative. The only hint is the schema note pointing to search_parliament_business for obtaining the ID, which is a lookup hint rather than usage guidance.

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