Skip to main content
Glama

Namentliche Abstimmungen

abstimmungen
Read-onlyIdempotent

Namentliche Abstimmungen im Bundestag, in einem Landtag oder im Europäischen Parlament, neueste zuerst, optional nach Stichwort: Ergebnis, Stimmen je Fraktion, Link zur Quelle und zum Gesetzgebungsverfahren bei Nexus Politics.

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": "abstimmungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
landNoNur bei ebene=land: Kürzel des Landes, z. B. „BY“
ebeneNoParlament: bund (Standard), land oder eu
suchbegriffNoStichwort in Titel oder Thema, z. B. „Wehrdienst“

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description provides rich behavioral context beyond the annotations. It explicitly states what data is included in the results (outcome, votes per faction, link to source/procedure) and specifies the underlying data source (Nexus Politics).

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?

The definition is presented in a single, highly dense sentence. It is exceptionally efficient, packing scope, ordering, and search functionality into one statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description is highly complete. It tells the AI exactly what the returned data will look like (e.g., result, faction votes, link) and where the data originates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema provides high coverage (100%), the description adds necessary semantics. It clarifies that 'suchbegriff' is specifically for the title or topic, helping the agent correctly formulate queries for that parameter.

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

Purpose5/5

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

The tool clearly identifies its resource ('Namentliche Abstimmungen') and specifies the scope (Bundestag, Landtag, European Parliament). It clearly describes the primary function: retrieving named votes.

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?

The description provides clear context for the tool's specific focus (named votes) and its default sorting order ('neueste zuerst'). While it does not explicitly list sibling tools to avoid, its specific resource focus guides the user effectively.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources