Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Parteifinanzen Österreich

get_at_parteifinanzen
Read-onlyIdempotent

Vergleicht eine Finanzposition (z. B. 'Geldspenden', 'Fördermittel', 'Sponsoring') aus den amtlichen Rechenschaftsberichten österreichischer Parteien (rechnungshof.gv.at). Aggregierte Summen, KEINE Einzelspender-Liste. Nicht alle Parteien haben ein maschinenlesbares XLSX veröffentlicht. [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": {
      "position": "<position>"
    },
    "name": "get_at_parteifinanzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional: Berichtsjahr
detailNoOptional: true für Rohzeilen bis Ortsgruppen-Ebene. Standard: false (aggregierte Partei-Summe)
positionYesFinanzposition, z. B. 'Geldspenden', 'Fördermittel', 'Sponsoring', 'Mitgliedsbeiträge'

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 readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real value beyond them: results are aggregated sums with NO individual donor list, and not all parties publish a machine-readable XLSX. This data-coverage caveat is exactly the kind of trait an agent needs before promising complete results. It stops short of describing error behavior or what happens when no XLSX exists for a party.

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?

Three tight sentences, front-loaded with what is compared and scoped immediately by the aggregation and availability caveats. The trailing bracketed note about delivering only original data from official sources is somewhat redundant with the rechnungshof citation but is short and reinforces provenance.

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 burden of describing returns and does so adequately: aggregated sums per position, no donor-level records, variable availability across parties. For a three-parameter read tool this is close to sufficient; only the shape of the comparison output itself is left unspecified.

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 three parameters are already documented structurally, establishing a baseline of 3. The description reinforces the meaning of `position` with concrete example values, but adds nothing about `year` or how `detail` (raw rows down to local branch level vs. aggregated party sum) changes the result beyond what the schema says.

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 names a specific verb and resource: it compares a financial position (e.g. Geldspenden, Fördermittel, Sponsoring) across the official Rechenschaftsberichte of Austrian parties, with the source (rechnungshof.gv.at) given. An agent can tell exactly what data comes back. It does not differentiate itself from any sibling tool, which keeps it at 4 rather than 5.

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 only implied: the reader infers this is for party-finance questions about a named position. There is no explicit when-to-use or when-not-to-use statement and no alternative tool is named. The caveats about aggregated data and missing XLSX files implicitly steer usage but are not framed as guidance.

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.