Skip to main content
Glama

Firmenwatch — Swiss Company Register

by ch.firmenwatch
OverviewDiscussionsAdmin

Tägliches Firmenbriefing

tagesbriefing
Read-onlyIdempotent

Liefert die wichtigsten strukturierten Firmenänderungen des jüngsten lückenlos verifizierten Publikationstags und zählt sie nach Art. Nutze dieses Werkzeug für einen täglichen KI-Lauf, ein Morgenbriefing oder eine automatisierte Marktbeobachtung. Optional lässt sich das Briefing nach Kanton, Meldungsart und Stichwort eingrenzen.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artenNoOptional auf Meldungsarten einschränken
datumNoOptionaler Publikationstag JJJJ-MM-TT. Ohne Angabe wird die jüngste lückenlos verifizierte Grenze verwendet.
anzahlNo
kantoneNoOptional auf Kantone einschränken
stichwoerterNoStichwörter im Firmennamen oder bereinigten Meldungstext

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNo
anzahlNo
fehlerNo
hinweisNo
quellenNo
begrenztNo
meldungenNo
datenstandNo
quellenhinweisNo
publikationstagNo
auswahl_nach_artNo
unvollstaendig_abNo
historienabdeckungNo
retry_after_secondsNo
datenqualitaetsstatusNo
lueckenlos_verifiziert_bisNo
neueste_verfuegbare_publikationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "oneOf": [
+    {
+      "required": [
+        "fehler"
+      ]
+    },
+    {
+      "not": {
+        "required": [
+          "fehler"
+        ]
+      },
+      "required": [
+        "publikationstag",
+        "anzahl",
+        "begrenzt",
+        "auswahl_nach_art",
+        "meldungen",
+        "datenstand",
+        "hinweis"
+      ]
+    }
+  ],
+  "properties": {
+    "anzahl": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "auswahl_nach_art": {
+      "additionalProperties": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "type": "object"
+    },
+    "begrenzt": {
+      "type": "boolean"
+    },
+    "code": {
+      "type": "string"
+    },
+    "datenqualitaetsstatus": {
+      "enum": [
+        "current",
+        "processing",
+        "degraded",
+        "unavailable"
+      ],
+      "type": "string"
+    },
+    "datenstand": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fehler": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "hinweis": {
+      "type": "string"
+    },
+    "historienabdeckung": {
+      "properties": {
+        "ab": {
+          "const": "2025-01-03",
+          "format": "date",
+          "type": "string"
+        },
+        "fruehere_stichtage_verfuegbar": {
+          "const": false,
+          "type": "boolean"
+        },
+        "vollstaendigkeit_zugesichert": {
+          "const": false,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "ab",
+        "vollstaendigkeit_zugesichert",
+        "fruehere_stichtage_verfuegbar"
+      ],
+      "type": "object"
+    },
+    "lueckenlos_verifiziert_bis": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "meldungen": {
+      "items": {
+        "properties": {
+          "amtlicher_beleg": {
+            "format": "uri",
+            "type": "string"
+          },
+          "art": {
+            "type": "string"
+          },
+          "art_code": {
+            "enum": [
+              "new_registration",
+              "name_change",
+              "address_change",
+              "seat_change",
+              "purpose_change",
+              "capital_change",
+              "legal_form_change",
+              "officer_added",
+              "officer_removed",
+              "auditor_change",
+              "liquidation_opened",
+              "liquidation_closed",
+              "deletion",
+              "bankruptcy_opened",
+              "bankruptcy_suspended",
+              "bankruptcy_closed",
+              "moratorium",
+              "debt_enforcement",
+              "branch_opened",
+              "branch_closed",
+              "merger",
+              "other"
+            ],
+            "type": "string"
+          },
+          "beschreibung": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "datum": {
+            "format": "date",
+            "type": "string"
+          },
+          "ereignis_id": {
+            "type": "string"
+          },
+          "firma": {
+            "type": "string"
+          },
+          "kanton": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ort": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "profil": {
+            "format": "uri",
+            "type": "string"
+          },
+          "rechtsform": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "uid": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "ereignis_id",
+          "datum",
+          "art",
+          "art_code",
+          "beschreibung",
+          "firma",
+          "uid",
+          "rechtsform",
+          "kanton",
+          "ort",
+          "profil",
+          "amtlicher_beleg"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "neueste_verfuegbare_publikation": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "publikationstag": {
+      "format": "date",
+      "type": "string"
+    },
+    "quellen": {
+      "properties": {
+        "aktualisierungen": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "url": {
+              "format": "uri",
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "url"
+          ],
+          "type": "object"
+        },
+        "stammdaten": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "url": {
+              "format": "uri",
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "url"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "stammdaten",
+        "aktualisierungen"
+      ],
+      "type": "object"
+    },
+    "quellenhinweis": {
+      "type": "string"
+    },
+    "retry_after_seconds": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "unvollstaendig_ab": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds meaningful context beyond this: it scopes the data to the 'jüngsten lückenlos verifizierten Publikationstag' and states that changes are 'nach Art' counted, plus 'wichtigsten' implying a selection/ranking. This gives an agent useful expectations about data freshness and aggregation boundaries without contradicting the 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?

Three sentences, each earning its place: the function, the usage, and the available filters. It is front-loaded with the primary deliverable and stays appropriately sized for a tool with five optional parameters and an output schema, with no redundant filler.

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?

Given the output schema exists and the annotations carry the safety profile, this description is largely complete: it explains what the tool returns (structured company changes with counts), the temporal scope, and the optional narrowing by canton/type/keyword. The term 'wichtigsten' is left ambiguous — an agent might not know how importance is determined — which is a minor gap, but overall the definition is adequate for correct invocation.

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 high at 80%, so the baseline is 3. The description merely restates what the schema already documents (filtering by Kanton, Meldungsart, Stichwort), and it adds no extra semantic nuance for 'anzahl' or 'datum'. It does not go beyond what the structured schema already provides.

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?

Description clearly states a specific verb-resource combination: 'Liefert die wichtigsten strukturierten Firmenänderungen des jüngsten lückenlos verifizierten Publikationstags und zählt sie nach Art.' This differentiates it from the sibling firm-specific tools (firma_details, firma_suchen, etc.) at a semantic level, but it does not name a sibling explicitly or state what it is not, so it falls just short of a 5.

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?

The description explicitly says when to use it: 'Nutze dieses Werkzeug für einen täglichen KI-Lauf, ein Morgenbriefing oder eine automatisierte Marktbeobachtung.' It provides clear target scenarios and mentions optional filtering, but it does not offer explicit exclusions or contrast with alternatives like the sibling tool definitions might expect.

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

All Firmenwatch — Swiss Company Register toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources