Skip to main content
Glama

Federal consultations (Vernehmlassungen)

search_consultations
Read-only

Search Swiss federal consultation procedures on draft laws and ordinances by keyword, status and language to see deadlines, lead offices and how stakeholders can respond.

Instructions

Federal consultation procedures (Vernehmlassungen / consultations / consultazioni) on draft laws and ordinances from Fedlex: title, description, status (planned, ongoing, closed, withdrawn), consultation period and lead federal office, newest first. Use it to see what legislation the Federal Council is preparing and until when stakeholders can respond. Example: {query: 'Energie', status: 'ongoing'}.

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_consultations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoWord in title or description (in the chosen language)
statusNoall
languageNode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds value by disclosing result ordering ('newest first'), the lifecycle status vocabulary, and the Fedlex source. It is silent on pagination, result counts, or coverage limits of the underlying dataset, which keeps it below the top band.

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 compact sentences ordered as identity → intended use → example, with no preamble or filler. Minor waste in re-listing the status enum values that the schema already constrains.

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 correctly carries the burden of describing the returned fields and their ordering, which it does. For a four-parameter read-only search tool this is close to sufficient; the remaining gap is guidance on result volume/paging and on when a different federal search tool is the better entry point.

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 only 25%, with just `query` documented in the schema; the description compensates partially by restating the status values and demonstrating a query+status combination. It says nothing about `limit` (default/max in schema only) or why `language` (de/fr/it) matters for matching the query string beyond the parenthetical in 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?

The description names a specific resource — Federal consultation procedures (Vernehmlassungen) on draft laws and ordinances from Fedlex — and enumerates the fields returned (title, description, status, consultation period, lead federal office). An agent can distinguish this from the law/gazette search siblings by the 'draft laws and ordinances / consultation period' framing, though no sibling 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?

'Use it to see what legislation the Federal Council is preparing and until when stakeholders can respond' gives a concrete use case, and the worked example ({query: 'Energie', status: 'ongoing'}) shows a realistic invocation. It stops short of stating when to prefer search_federal_law or search_federal_gazette instead, so it lands at clear-context-no-exclusions.

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