Skip to main content
Glama
Sign In

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

by io.consiliumos
OverviewDiscussionsAdmin

MdEP-Profil

get_mep_profile
Read-onlyIdempotent

Gibt das 360°-Profil eines Europaabgeordneten (MdEP) zurück — Land, EU-Fraktion, nationale Partei, Ausschüsse, Kontakt/Hintergrunddaten (E-Mail, Foto, Geburtsort), Website und Social-Media-Konten, Abstimmungszahl und Fraktionstreue sowie eine Kurzfassung der Plenar-Aktivität (belegte Sitzungstage, Reden, Anfragen an Kommission/Rat). Alle 27 EU-Länder abgedeckt. Hintergrunddaten (Ausschüsse, E-Mail, Foto, Social Media) werden wöchentlich nachgeladen — bei ganz neu erfassten MdEPs ggf. noch nicht vorhanden, siehe Datenqualitäts-Hinweis in der Antwort. Die deutschen Texte der EU-Plenarreden sind zu 88,5 % maschinelle Übersetzungen des EP-Wortprotokolls; nur bei deutschsprachig gehaltenen Reden ist der gespeicherte Text der Originalwortlaut. Für wörtliche Zitate die Originalsprache heranziehen — search_eu_speeches kennzeichnet jede Rede einzeln. Jeder Treffer nennt am Ende der Antwort seine Beleg-Seite und das Original. Gib beide Links an und zitiere mit dem Titel des Treffers. [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": {
      "mep_name": "<mep_name>"
    },
    "name": "get_mep_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
mep_nameYesName des MdEP, z. B. 'Manfred Weber'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond annotations (readOnly, idempotent, non-destructive, closed-world) by disclosing that background data is reloaded weekly and may be absent for newly registered MEPs, that a data-quality note appears in the response, and that German speech texts are 88.5% machine translations of the EP transcript. It also states each hit self-cites its Beleg-Seite and original source, which tells the agent how to attribute output.

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?

Front-loaded with the returned data, then caveats, then citation policy, so readers get the essentials first. It is dense and slightly repetitive (background data fields are listed twice, e.g. E-Mail and Foto), and the bracketed 'Ohne KI' disclaimer is tacked on, but nearly every sentence contributes information.

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?

No output schema exists, so the description carries the full burden and does so: it enumerates the response sections, flags missing-data situations, explains translation provenance, and specifies the attribution links returned. For a single-parameter read tool with a rich composite payload, nothing an agent needs in order to call and interpret it 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% for the single parameter, with an inline description and a concrete example ('Manfred Weber'), so the schema already carries the semantics. The description adds no input-format guidance (e.g. whether partial or non-German names work), which is the correct baseline 3 when the schema does the work.

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?

Names a specific verb and resource (returns the 360° profile of an MEP) and enumerates the returned content: country, EU group, national party, committees, contact/background data, website, social media, vote counts, group loyalty, and plenary activity summary. The scope statement 'Alle 27 EU-Länder abgedeckt' further pins it down, so an agent can distinguish it from get_mdb_profile (Bundestag) or search_mep without opening a schema.

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?

Gives clear situational guidance for the translation caveat: for verbatim quotes use the original language, and search_eu_speeches flags each speech individually. It also instructs to always give both links and cite with the title. What is missing is guidance on prerequisites, e.g. using search_mep to resolve an ambiguous mep_name before calling.

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

All ParliamentOS – Bundestag, Landtage, Nationalrat, EU toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources