Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Länderposition im EU-Parlament

get_country_position
Read-onlyIdempotent

Zeigt, wie die Abgeordneten EINES Landes im Europaparlament abgestimmt haben — quer über alle Fraktionen. Beantwortet 'Wie hat die deutsche Delegation gestimmt?' inklusive Geschlossenheit und Abweichung von der EP-Mehrheit. Ergänzt get_mep_vote (eine Person) und compare_eu_groups (eine Fraktion) um den nationalen Blickwinkel. Die Einzelabstimmungen reichen über die Wahlperioden 9 und 10 (ab 15.07.2019); die Gesamtbilanz am Anfang der Antwort gilt für die laufende Wahlperiode 10. WICHTIG: Eine Länderdelegation ist NICHT die Position der jeweiligen Regierung — MdEP sind nach Fraktionen organisiert, gespaltene Delegationen sind der Normalfall. [Ohne KI: liefert ausschließlich Originaldaten aus amtlichen Quellen.]

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": {
      "country": "<country>"
    },
    "name": "get_country_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl Abstimmungen, max. 25. Standard: 5
topicNoOptional: Suchbegriff im Abstimmungstitel, z. B. 'Klima', 'Asyl', 'Lieferkette'
countryYesLändercode, z. B. 'DE', 'AT', 'FR' (ISO2; ISO3 wie 'DEU' wird ebenfalls akzeptiert)
date_fromNoOptional: nur Abstimmungen ab diesem Datum (YYYY-MM-DD)
main_onlyNoNur Hauptabstimmungen (Schlussabstimmungen). Standard: true — mit false auch Änderungsanträge, dort zeigen sich Delegationsspaltungen am deutlichsten.

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?

Beyond the annotations (read-only, idempotent, non-destructive), the description discloses data coverage across parliamentary terms 9 and 10 from 15.07.2019, and notes that the overall summary at the start of the response applies to the current term 10. It also clarifies the conceptual scope of 'country position' and states that the tool returns original data from official sources.

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 description is front-loaded with the core purpose and organized around scope, alternatives, temporal coverage, and caveats. It is somewhat long, and the bracketed 'Ohne KI' provenance sentence is not necessary for tool selection, but the remaining content earns its place.

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?

For a five-parameter analytical tool with no output schema, the description supplies the temporal scope, the distinction from related tools, the main conceptual warning, and a hint that the response includes an overall summary plus cohesion/deviation metrics. It is complete enough for an agent to invoke it correctly without mistaking the result for a government position.

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 the input schema already documents all five parameters, including defaults and formats. The description mentions cohesion, deviation, and split delegations, which lightly contextualizes the main_only distinction, but it does not add parameter-specific semantics beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb and resource: it shows how the members of one country voted in the European Parliament across all groups. It gives a concrete example question ('Wie hat die deutsche Delegation gestimmt?') and explicitly distinguishes itself from get_mep_vote (one person) and compare_eu_groups (one group).

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

Usage Guidelines5/5

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

Names the sibling tools and explains the national-delegation angle they do not cover, which tells an agent when to choose this tool. It also adds an important usage caveat: a country delegation is not the position of that country's government, and split delegations are normal.

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.