Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Social-Media-Kennzahlen

get_social_stats
Read-onlyIdempotent

Zeigt die aktuellen Follower-Zahlen eines Abgeordneten auf Instagram, sofern vorhanden auch TikTok und Twitter/X, sowie die Veränderung innerhalb der letzten 30 Tage, sofern für diesen Zeitraum mindestens zwei Messpunkte vorliegen. Liegen keine vor, sagt der Output das ausdrücklich und nennt das Alter des letzten Messpunkts. Die Follower-Pipeline erreicht derzeit nicht alle Profile (Stand 03.08.2026: rund ein Drittel der Instagram-Profile ist aktuell, der Rest älter als 30 Tage) — Stand und Lücke stehen deshalb immer dabei. Die X/Twitter-Ingest-Pipeline liefert für nahezu alle Abgeordneten keine Daten; der Output kennzeichnet das explizit statt die Plattform stillschweigend wegzulassen. [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_social_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
mdb_nameYesName des Abgeordneten, z. B. 'Felix Banaszak'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

The annotations already declare this a safe, idempotent read, so the extra detail here is genuinely additive: pipeline coverage (~one third of Instagram profiles current, the rest older than 30 days), near-total absence of X/Twitter data, and the explicit promise that the output flags missing measurement points and reports the age of the last data point. Freshness and data-gap behaviour is exactly what an agent needs to interpret results correctly.

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 capability and the 30-day-delta condition are front-loaded, and caveats follow in a logical order. There is mild repetition (the coverage gap is stated, then restated) and the bracketed 'Ohne KI' boilerplate adds no operational value, but nothing is confusing or buried.

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?

For a single-parameter read-only tool with no output schema, the description covers everything needed: what is returned per platform, when a delta is computable, what happens when it is not, and how systemic data gaps are surfaced in the output. An agent can call this and correctly interpret a partial or empty result.

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?

There is only one parameter, mdb_name, and the schema already documents it at 100% coverage with an example value. The description adds nothing about name format, aliases, or matching behaviour, so the baseline of 3 for high schema coverage applies.

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?

The description names a specific resource and scope: current follower counts for an MP on Instagram, plus TikTok and X/Twitter where available, together with the 30-day change. That is precise enough to separate it from the neighbouring profile and vote tools (e.g. get_mdb_profile) without opening any schema.

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?

Usage is implied rather than guided: an agent can infer it should call this to obtain social-media metrics for a named MP, and the text explains the conditions under which a 30-day delta exists. However, no alternative tool is named and no when-not-to-use case is stated, so routing still rests on 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.