Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Petitionen Österreich suchen

search_at_petitionen
Read-onlyIdempotent

Durchsucht österreichische Petitionen und Bürgerinitiativen im Nationalrat nach Thema. Zeigt Titel, Typ, Status-Phase und Themenkategorien. Gesucht wird ausschließlich im TITEL und nur am Wortanfang (query='Tier' findet 'Tierschutz', nicht 'Dotierung') — Volltexte der Einbringungen liegen nicht vor. 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_at_petitionen"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional: 'petition' oder 'buergerinitiative' ('Petition'/'Bürgerinitiative' werden ebenfalls erkannt). Ein unbekannter Wert liefert eine Fehlermeldung mit den gültigen Werten, keine leere Liste.
limitNoAnzahl Ergebnisse. Standard: 10
queryNoOptional: Suchbegriff im Titel, z. B. 'Klimaschutz'. Match am Wortanfang, Komposita eingeschlossen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low; the description instead adds real behavioral detail: title-only prefix matching with a concrete example ('Tier' vs 'Dotierung'), absence of full texts, and what each hit will contain (Titel, Typ, Status-Phase, Themenkategorien, Beleg-Seite plus Original). It does not discuss pagination or the shape of an empty result, which keeps it from a 5.

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-loads the core purpose, then constraints, then citation requirements, with no filler sentences. The trailing bracketed note about 'Ohne KI' is promotional rather than operational and slightly dilutes the otherwise tight structure.

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?

For a three-parameter read-only search with no output schema, the description covers corpus, matching rules, returned fields, and citation obligations – enough to call it correctly. Minor gaps remain around result limits and error/empty behavior, though the schema partially covers the limit.

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 the schema already documents all three parameters including the enum-like values for 'type' and the prefix-match semantics of 'query'. The description restates the prefix-match rule with an additional example but adds no meaning the schema lacks, so the baseline 3 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?

States a specific verb and resource ("Durchsucht österreichische Petitionen und Bürgerinitiativen im Nationalrat nach Thema") and pins the exact scope of the search corpus and match mode. An agent can tell this apart from sibling document/begutachtung searches because the target collection is named explicitly.

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?

Makes clear when this tool applies (topic search over petitions and citizen initiatives) and gives a strong exclusion signal: 'Volltexte der Einbringungen liegen nicht vor', telling the agent not to use it for full-text lookups. It never names an alternative tool for full-text needs, so the routing guidance stops short of explicit alternatives.

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.