amtsblatt-mcp

Overview Schema Source Related Servers Discussions Admin

gazette_search_procurement

Read-onlyIdempotent

Find public tender notices published in Swiss cantonal gazettes for procurement (Submissionen), limited to cantons AR, TI, BS, BL, VS, and ZG.

Instructions

<use_case>Find public tenders published in the gazette (Submissionen) — the procurement-specific entry point. Note only AR, BS, TI, ZG, BL and VS mirror tenders here; for full Swiss coverage including Zurich use swiss-procurement-mcp.</use_case>

Sucht öffentliche Ausschreibungen (Beschaffungswesen/Submissionen).

Beschaffung ist ausschliesslich eine KANTONALE Rubrik (OB-<Kanton>), nicht föderal. Nur wenige Kantone publizieren sie hier: AR und TI (aktiv) sowie BS, BL, VS, ZG (inaktiv — BS/BL/VS nur Archiv, ZG leer).

WICHTIG — Spiegel vs. Original: Die OB-*-Rubriken sind praktisch vollständig Zweitpublikationen von simap.ch-Ausschreibungen (gemessen über den OB-TI-Jahrgang 2026: 92,1 % tragen eine simap-Publikationsnummer). Wer Beschaffung sucht, ist mit swiss-procurement-mcp an der Primärquelle besser bedient — alle 26 Kantone plus Bund, mit CPV- und BKP-Codes, Zuschlägen und Publikationsverlauf.

Was es NUR hier gibt, sind die Beschaffungs-Subrubriken AR-VS40 (Wallis, Zuschläge), AR-OW40 (Obwalden) und BA-SH40 (Schaffhausen) sowie die Ticiner Subrubrik OB-TI65 («Avvisi di gara non CIAP»): keine davon trägt eine simap-Nummer. Kanton VS, OW und SH liefern deshalb Treffer, obwohl sie keine aktive OB-*-Rubrik haben. Die meisten Kantone — inklusive Zürich — publizieren Ausschreibungen über simap.ch, das NICHT Teil dieser Quelle ist; eine Abfrage für einen solchen Kanton liefert eine Erklärung statt eines leeren Ergebnisses. Die Quelle kennt keine CPV-Codes.

Args: params (ProcurementInput): - keyword (Optional[str]): Freitext (kein CPV-Code) - canton (Optional[str]): Kantonskürzel; ohne Angabe alle aktiven - date_start / date_end (Optional[str]): Zeitraum YYYY-MM-DD - include_inactive (bool): inaktive Rubriken (BL/BS/VS/ZG) einbeziehen - limit (int): 1–100 (Standard 20), page (int): 0-basiert - language (str), only_language (bool), response_format (str)

Hinweis zur Trefferzahl: Ticino publiziert überwiegend it/fr, Appenzell A.Rh. de/fr — je Sprache ein eigener Datensatz mit eigener Publikationsnummer. Identische Titel werden zusammengefasst, übersetzte bleiben getrennt; die Trefferzahl kann daher über der Zahl verschiedener Ausschreibungen liegen. only_language=True erzwingt eine einzelne Sprachfassung.

Returns: str: Ausschreibungen (neueste zuerst) mit Datum, Kanton, Titel, Sprache, ID.

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.17.0Jul 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), the description adds critical behavioral context: that results come from simap.ch mirror, which cantons are active/inactive, language duplication behavior, and unique subrubrics. No contradictions with annotations.

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?

Well-structured with sections and bullet points. However, it is somewhat lengthy and repeats language behavior details. Could be more concise, but the structure aids readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive: covers data source, canton coverage, language handling, pagination, unique features (subrubrics without simap numbers), comparison with alternative tool, and return format. Given complexity and presence of annotations/output schema, nothing essential is missing.

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?

Despite schema description coverage being 0%, the description includes a detailed Args section that explains each parameter's purpose and constraints (e.g., 'kein CPV-Code', 'Freitext'). Adds context beyond schema property descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: finding public tenders (Submissionen) in the gazette. It specifies procurement-specific entry point and distinguishes from siblings by noting it's for procurement. It also mentions which cantons are covered and points to an alternative for full Swiss coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Excellent guidance: explicitly states when to use this tool (for gazette procurement), when not to use it (full Swiss coverage requires swiss-procurement-mcp). Details limitations (only certain cantons, no CPV codes, duplicate entries due to languages) and gives alternative tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server