Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

EU-Förderung einer Region

get_eu_regional_story
Read-onlyIdempotent

Die Regional-Story (M-9): verbindet EU-Kohäsionsförderung in einer Region mit dem Abstimmungsverhalten der Länderdelegation im EP zu Kohäsionspolitik (REGI-Dossiers). Beantwortet 'Wie viel EU-Geld fließt in meine Region — und wie stimmen unsere Abgeordneten dazu ab?'. Für Deutschland bis auf Bundestagswahlkreis-Ebene, für Österreich bis Landeswahlkreis-Ebene. Ideal als Briefing-/Newsletter-Baustein. [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_eu_regional_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl Regionen/Abstimmungen je Sektion, max. 15. Standard: 5
periodNoFörderperiode: '2021-2027' (Standard) oder '2014-2020'
countryYes'DE'/'Germany' oder 'AT'/'Austria'
bundeslandNoOptional (nur AT): Bundesland, z. B. 'Steiermark'
wahlkreis_nrNoOptional (nur DE): Bundestagswahlkreis-Nummer 1-299 für die Förder-Sektion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behaviour, so the safety profile is covered. The description adds genuinely new context: the geographic resolution per country (Bundestagswahlkreis level for DE, Landeswahlkreis level for AT) and that output is exclusively original data from official sources without AI generation. It does not describe the response structure or how the two sections are ordered.

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 core definition is front-loaded in the first sentence and the geographic scope and use case follow logically. The internal label '(M-9)' and the bracketed '[Ohne KI: ...]' provenance note are somewhat incidental, but the text remains compact and free of padding.

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?

With no output schema and five parameters, the description does the important work of explaining what the tool combines, the per-country granularity, and the intended deliverable. What is missing is a sketch of the returned sections (funding vs. votes) and their relationship to the limit parameter, which an agent would need to set expectations.

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 every parameter including limit, period, country, bundesland and wahlkreis_nr is already documented in the schema, establishing a baseline of 3. The description's note on DE/AT granularity adds some orientation for the region parameters, but it does not explain limit, period defaults or how the two sections consume limit, so it adds little beyond the schema.

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 concrete resource and a concrete combination of data: EU cohesion funding for a region joined with the voting behaviour of national EP delegations on REGI dossiers, plus the exact question it answers. This is far more specific than a restatement of the name. It stops short of a 5 because it never names the obvious sibling (get_eu_cohesion_funding) that provides funding alone, leaving the boundary to be inferred.

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?

It states the question the tool answers ('Wie viel EU-Geld fließt in meine Region — und wie stimmen unsere Abgeordneten dazu ab?') and suggests a use case ('Ideal als Briefing-/Newsletter-Baustein'), which implies when to reach for it. However, there is no explicit when-not guidance and no named alternative for callers who only want funding figures or only want voting records.

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.