Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Abgeordnetenprofil

get_mdb_profile
Read-onlyIdempotent

Gibt das vollständige Profil eines Abgeordneten zurück — Bundestag Deutschland (Standard) oder Nationalrat/Bundesrat Österreich (country='AT'). Foto, Fraktion/Klub, Wahlkreis, Mandate (DE zusätzlich Bundesland, Social-Media-Handles, Regierungsamt laut Rednerrolle im Plenarprotokoll mit Beleg-ID und Stand). Nur DE: gemessenes Sprechtempo (Wörter/Minute aus Plenarreden; Daten: openparliament.tv, Open Database License (ODbL) 1.0) samt Redelänge-Kalibrierung — damit lässt sich ein Redemanuskript exakt auf die vorgegebene Redezeit dieses Abgeordneten zuschneiden. 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": {
      "mdb_name": "<mdb_name>"
    },
    "name": "get_mdb_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoLand: 'DE' (Standard) oder 'AT'
mdb_nameYesName des Abgeordneten

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 read-only, idempotent, non-destructive behavior, so the bar is low; the description still adds real context by listing the profile payload, disclosing the data source and ODbL license, and imposing a citation contract (source page plus original link, quote with the hit title). It does not explain matching/ambiguity behavior when mdb_name is not unique or not found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payload description is front-loaded well, but the single dense paragraph mixes return contents, country branching, tempo calibration, licensing, and citation rules. The bracketed 'Ohne KI' sentence is boilerplate that adds little, and the tempo/Redemanuskript aside is verbose.

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, the description carries the return-value burden and does so by enumerating the fields and the DE-only extras. It is nearly complete for a two-parameter read tool; only failure/no-match behavior and output format specifics are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining what country actually switches (DE vs AT) and which fields are DE-only (Bundesland, social handles, speaking-rate calibration), which is meaning the schema does not convey.

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 ('Gibt das vollständige Profil eines Abgeordneten zurück') and enumerates the returned fields, so the agent knows exactly what it gets. It also scopes the tool to Bundestag DE by default and Austria via country='AT', which separates it from the MEP-oriented siblings, though it never names get_mep_profile explicitly.

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 DE-default / AT-via-country rule is clear usage context, and the Austria variant is called out. However, there is no guidance on when to prefer this over get_mep_profile, get_wahlkreis_profile, or search_mdb for finding a name, leaving sibling routing to inference.

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.

Resources