Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

MdEP suchen

search_mep
Read-onlyIdempotent

Sucht Europaabgeordnete (MdEP) nach Name, Land oder EU-Fraktion — alle 27 EU-Länder, alle ~719 aktuellen MdEPs (seit 24.07.26 volle Abdeckung, zuvor nur DE+AT). Gibt Profildaten mit nationaler Partei und EU-Fraktion zurück. 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

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional: Name oder Teilname
limitNoAnzahl Ergebnisse, max. 20. Standard: 10
countryNoOptional: ISO2-Ländercode, z. B. 'DE', 'AT', 'FR', 'PL'. Ohne Angabe: alle 27 Länder.
political_groupNoOptional: EU-Fraktion. Amtliche Kürzel der laufenden Wahlperiode: 'PPE', 'S&D', 'PfE', 'ECR', 'Renew', 'Verts/ALE', 'The Left', 'ESN', 'NI'. Geläufige deutsche Namen werden aufgelöst ('EVP' → PPE, 'Grüne/EFA' → Verts/ALE, 'EKR' → ECR).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds real value beyond that: the coverage scope and its effective date, the shape of returned profile data (national party + EU group), and the per-hit source/original links. It does not cover result ordering, pagination behavior beyond the limit parameter, or what an empty result looks like.

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?

Purpose and coverage are front-loaded in the first sentence, followed by return content and then citation rules, which is a sensible order. The trailing bracketed note about 'ohne KI' is tangential for an agent and the citation instructions ('Gib beide Links an') are directive rather than descriptive, but neither bloats the text much.

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?

There is no output schema, and the description compensates by naming the returned fields (national party, EU group) and the per-hit source page and original link. Combined with the coverage caveat, an agent knows enough to call and cite correctly; only pagination/ordering and empty-result behavior are left unspecified.

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 all four parameters (including the limit default of 10 / max 20 and the ISO2 country examples and official group abbreviations) are already documented. The description restates the filter axes and the 'all 27 countries' default without adding format or matching semantics (e.g. partial-name matching, case handling) 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?

States a specific verb and resource ('Sucht Europaabgeordnete (MdEP)') plus the three filter axes (Name, Land, EU-Fraktion) and the coverage scope (~719 MEPs, all 27 countries, with a date for the coverage change). It is unambiguous what the tool does, but it never contrasts itself with the closely named sibling get_mep_profile, so an agent must infer that this is the list/search side of the pair.

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?

The description implies when to use it (when you have a name, country, or political group) and the schema notes that omitting country searches all 27. There is no explicit when-not guidance and no mention of get_mep_profile as the alternative for a single MEP's full record, which is the most likely misuse path given the sibling names.

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.