Skip to main content
Glama

Search the Federal Gazette (BBl)

search_federal_gazette
Read-only

Search Swiss Federal Gazette publications by title keyword and date range to find Federal Council dispatches, draft acts, referendum texts, reports and notices, with BBl references and Fedlex links.

Instructions

Search publications in the Federal Gazette (Bundesblatt BBl / Feuille fédérale FF / Foglio federale FF): Federal Council dispatches (Botschaften) on new bills, draft federal acts and decrees, referendum texts, reports and official notices. Filter by title keyword and publication-date range; returns date, title, BBl reference (e.g. 'BBl 2024 1234') and Fedlex link, newest first. Examples: {query:'Botschaft'}; {query:'Klima', date_from:'2023-01-01'}; {query:'énergie', language:'fr'}.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoTitle keyword in the chosen language, e.g. 'Botschaft', 'Datenschutz'
date_toNoLatest publication date (default: today)
languageNode
date_fromNoEarliest publication date (default: 90 days before date_to, or 2 years with a query; range max 2 years)

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 and openWorldHint, so the safety profile is covered; the description adds the useful facts that results are sorted newest first and carry date, title, BBl reference and Fedlex link. Pagination beyond the limit parameter and coverage limits of the index are not discussed.

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-loaded with purpose and coverage, then filtering behavior, then compact inline examples with no filler sentences. The examples are dense but each one demonstrates a distinct parameter combination, so they earn their space.

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 usefully spells out the returned fields, and it explains the domain vocabulary (BBl, Botschaften). Missing are edge behaviors an agent would want: what a call with no query returns, whether the 2-year range cap is enforced, and how limit interacts with result ordering.

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 60%, and the description reinforces query (title keyword in the chosen language), the date range, and language, with the 'énergie'/'fr' example implicitly signalling that the query must be in the selected language. limit is left entirely to the schema, and accent/matching semantics are implied rather than stated, so the baseline 3 fits.

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 verb (search) and resource (Federal Gazette/BBl/FF publications) and enumerates the content types covered: Federal Council dispatches, draft acts, referendum texts, reports, official notices. This lets an agent distinguish it from consolidated-law tools, 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?

Three worked examples show realistic call shapes (bare keyword, keyword plus date_from, keyword plus language), which conveys when the tool is appropriate and how filters combine. However, it never states when not to use it, e.g. that consolidated federal law belongs to search_federal_law or draft-stage items to search_consultations.

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