Skip to main content
Glama

Petitionen auf Nexus Politics

petitionen
Read-onlyIdempotent

Öffentliche Petitionen auf Nexus Politics an Gemeinde, Land, Bund oder EU: laufende (sammeln Unterschriften) oder beendete, optional für eine Postleitzahl und nach Stichwort. Mit Empfänger, Unterschriften, Ziel, Frist und Link zum Unterschreiben; ohne Petitionstext und ohne Namen.

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

Input Schema

NameRequiredDescriptionDefault
plzNoDeutsche Postleitzahl mit fünf Ziffern, z. B. „10117“
statusNolaufend (Standard, sammelt Unterschriften) oder beendet (beendet, übergeben oder beantwortet)
suchbegriffNoStichwort im Betreff oder Empfänger, z. B. „Radweg“

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so safety is covered. The description adds real value by disclosing the response shape (Empfänger, Unterschriften, Ziel, Frist, Link) and, importantly, that the petition text and signer names are NOT returned, but it says nothing about result volume, ordering or pagination.

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?

A single dense, front-loaded sentence that puts scope first, then filters, then the returned fields and their exclusions. Minimal waste; only the level enumeration is slightly 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?

No output schema exists, and the description compensates by enumerating the returned fields and explicitly stating what is excluded (no petition text, no names), which is exactly what an agent needs before calling. Only the lack of any hint about result volume or ordering keeps it from a 5.

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%, including the enum semantics for status, so the schema carries the parameter burden. The description only restates the filtering idea without adding format details (e.g. whether the PLZ filters by recipient region or by signer location), so it adds little beyond the schema.

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 concrete resource (öffentliche Petitionen) with explicit scope (Gemeinde, Land, Bund, EU) and the two states it covers (laufend/beendet). It is distinguishable from most siblings, though the mention of EU-level petitions overlaps in subject matter with eu_buergerinitiativen without clarifying the difference.

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?

Gives implied usage through the optional filters (Postleitzahl, Stichwort) and notes that 'laufend' is the default via the schema, but there is no explicit when-to-use/when-not guidance and no naming of an alternative tool for related queries.

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