Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Abgeordnete suchen

search_mdb
Read-onlyIdempotent

Sucht Abgeordnete nach Name, Fraktion, Bundesland oder Wahlkreis — Bundestag Deutschland (Standard) oder Nationalrat/Bundesrat Österreich (country='AT'). Gibt Profildaten mit Foto-URL zurück (DE zusätzlich mit Social-Media-Handles). 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_mdb"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional: Name oder Teilname
limitNoAnzahl Ergebnisse. Standard: 10
countryNoLand: 'DE' (Standard, Bundestag) oder 'AT' (Nationalrat/Bundesrat)
fraktionNoOptional: Fraktion/Klub, z. B. 'SPD', 'CDU/CSU', 'Grüne', 'FDP', 'AfD', 'BSW' (DE) oder 'ÖVP', 'SPÖ', 'FPÖ', 'GRÜNE', 'NEOS' (AT)
wahlkreisNoOptional: Wahlkreisname oder -nummer (DE) bzw. Regionalwahlkreis (AT)
bundeslandNoOptional: Bundesland (DE) bzw. Landeswahlkreis (AT)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and determinism are covered. The description adds genuinely new behavior: results include profile data with photo URL, DE additionally social-media handles, and every hit carries a Beleg-Seite and Original link that the agent must cite with the hit's title. That is useful, but it is largely output/citation procedure rather than tool-side behavior such as pagination or empty-result handling.

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 purpose and the DE/AT switch, then return contents, then the citation obligation. Dense but each clause carries information; the bracketed 'Ohne KI' note is marginal filler relative to the rest.

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 six optional parameters, no output schema and no required arguments, the description does a good job covering what is returned (profile fields, photo URL, DE social handles) and what the agent must do with the links. What remains thin is result-count/empty-result behavior and the exact citation format, which an agent may have to guess.

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 six parameters are already documented in the input schema, and the description's mention of Name, Fraktion, Bundesland, Wahlkreis and country largely restates them. It adds no semantics for 'limit' or for matching behavior (partial name matching, case handling), so the baseline of 3 applies.

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?

Specific verb plus resource ('Sucht Abgeordnete') and it enumerates the searchable facets (Name, Fraktion, Bundesland, Wahlkreis) and the two data domains (DE Bundestag default, AT Nationalrat/Bundesrat via country='AT'). It does not explicitly distinguish itself from the sibling get_mdb_profile (single-profile fetch) or search_mep, so an agent must infer the boundary from names alone.

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 selection context: default is the German Bundestag, and country='AT' switches to the Austrian chambers; the filter list implies what queries are supported. It stops short of stating when NOT to use it (e.g. use get_mdb_profile once an id is known), so no alternative is named.

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.