Skip to main content
Glama

Europäische Bürgerinitiativen

eu_buergerinitiativen
Read-onlyIdempotent

Europäische Bürgerinitiativen aus dem Register der EU-Kommission: laufende (mit Unterschriften und Frist) oder von der Kommission beantwortete, optional nach Stichwort gefiltert.

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

Input Schema

NameRequiredDescriptionDefault
statusNo
suchbegriffNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered structurally. The description does add value by disclosing what accompanies 'laufend' entries (Unterschriften und Frist), which is behavioural detail the annotations cannot convey. It says nothing about result volume, pagination, or freshness of the register snapshot, so the addition is real but partial.

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?

A single front-loaded sentence with the resource and source first, then the two states, then the optional filter. The colon-based elaboration does real work without filler or repetition.

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 two-optional-parameter read-only lookup with no output schema, the definition covers origin, the meaning of both filter dimensions, and partial return content. Only the shape and volume of results remain unstated, which is a minor gap given the annotations already signal a safe, idempotent read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it largely does: it glosses the 'laufend'/'beantwortet' enum as running initiatives with signatures and deadline versus Commission-answered ones, and marks 'suchbegriff' as an optional keyword filter. What is missing is any hint about keyword matching behaviour (substring, language, title vs. full text) for a free-text parameter.

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 specific resource (Europäische Bürgerinitiativen) and its source (Register der EU-Kommission), plus the two content states it returns (laufend mit Unterschriften und Frist vs. von der Kommission beantwortet). That is a clear verb-less but unambiguous retrieval purpose; it does not explicitly name a sibling for differentiation, so it stops short of 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 implied by the two enumerated states and the 'optional nach Stichwort gefiltert' hint, which tells the agent filtering is optional and full-register retrieval is the default. There is no explicit when-to-use/when-not guidance and no pointer to a competing tool such as petitionen or beteiligungsverfahren, which an agent might plausibly confuse with this one.

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