Skip to main content
Glama
Sign In
parlament-at

parlament-at

by bernhardbrugger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Lebenslauf und Mandate einer Person im Parlament

parl_person
Read-onlyIdempotent

Look up a person’s mandates, functions, party club, current office status, and short biography—birth, political roles, career, education—from Austrian Parliament open data.

Instructions

Zeigt zu einer Person (pad_intern oder Name) die Mandate und Funktionen mit Zeiträumen, den Klub, ob sie aktuell im Amt ist, sowie Kurzbiografie (Geburt, politische Funktionen, Werdegang, Bildung) laut Parlament. Die Biografien beruhen ab 1945 auf Angaben der Mandatarinnen und Mandatare selbst. Quelle: offene Daten des Parlaments (CC BY 4.0).

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

Input Schema

NameRequiredDescriptionDefault
nameNoName, falls pad_intern unbekannt (bei Mehrdeutigkeit werden Kandidaten genannt)
pad_internNoNummer der Person aus parl_abgeordnete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds genuinely non-derivable context: biographies are self-reported by MPs and only date back to 1945, plus the CC BY 4.0 source — useful data-quality caveats for an agent judging reliability.

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

Conciseness5/5

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

Three sentences with zero padding: the returned data is front-loaded, then the data-quality caveat, then provenance. Every clause carries distinct information an agent can act on.

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 compensates by enumerating the returned fields, and it covers provenance and data limitations. Only the ambiguity/fallback behaviour, though present in the schema, is not echoed in the description and the relationship to sibling person-tools is unaddressed.

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%, with both parameters fully described including the ambiguity behaviour ('bei Mehrdeutigkeit werden Kandidaten genannt'). The description only restates that either pad_intern or name identifies the person, adding no syntax or precedence detail beyond the schema, so baseline 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?

The description states a specific verb ('Zeigt') and resource (a person) and enumerates exactly what is returned: mandates and functions with time periods, club, current-office status, and a short biography. That is far more specific than the title alone, though it never contrasts itself with siblings like parl_abgeordnete or parl_reden_person.

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 by the accepted inputs ('zu einer Person (pad_intern oder Name)'), so an agent can infer it is the lookup tool when a person's mandates/biography are needed. There is no explicit when-to-use/when-not guidance and no mention of the sibling tools that also take a person, so the agent must pick between them unaided.

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

Deploy Server

Other Tools