Firmenwatch — Swiss Company Register

Schweizer Firma suchen

firma_suchen

Read-onlyIdempotent

Sucht Firmen im Schweizer Handelsregister nach Name oder UID. Liefert Firma, UID, Rechtsform, Sitz, Adresse und Status. Nutze dies, wenn die UID nicht bekannt ist.

Input Schema

TableJSON Schema

Name	Required	Description
`anzahl`	No	Höchstzahl Treffer, 1 bis 25
`kanton`	No	Kantonskürzel, z. B. ZH. Erlaubt: AG, AI, AR, BE, BL, BS, FR, GE, GL, GR, JU, LU, NE, NW, OW, SG, SH, SO, SZ, TG, TI, UR, VD, VS, ZG, ZH
`status`	No	Auf einen Status einschränken
`suchbegriff`	Yes	Firmenname oder Teil davon, oder eine UID wie CHE-123.456.789

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`fehler`	No
`firmen`	No
`hinweis`	No
`quellen`	No
`datenstand`	No
`quellenhinweis`	No
`treffer_gesamt`	No
`weitere_treffer`	No
`unvollstaendig_ab`	No
`historienabdeckung`	No
`retry_after_seconds`	No
`datenqualitaetsstatus`	No
`lueckenlos_verifiziert_bis`	No
`neueste_verfuegbare_publikation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "oneOf": [
+    {
+      "required": [
+        "fehler"
+      ]
+    },
+    {
+      "not": {
+        "required": [
+          "fehler"
+        ]
+      },
+      "required": [
+        "treffer_gesamt",
+        "weitere_treffer",
+        "firmen",
+        "datenstand",
+        "datenqualitaetsstatus",
+        "hinweis"
+      ]
+    }
+  ],
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "datenqualitaetsstatus": {
+      "enum": [
+        "current",
+        "processing",
+        "degraded",
+        "unavailable"
+      ],
+      "type": "string"
+    },
+    "datenstand": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fehler": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "firmen": {
+      "items": {
+        "properties": {
+          "adresse": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "firma": {
+            "type": "string"
+          },
+          "kanton": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "letzte_meldung": {
+            "format": "date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "profil": {
+            "format": "uri",
+            "type": "string"
+          },
+          "rechtsform": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sitz": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "enum": [
+              "active",
+              "in_liquidation",
+              "bankrupt",
+              "deleted"
+            ],
+            "type": "string"
+          },
+          "uid": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "firma",
+          "uid",
+          "rechtsform",
+          "sitz",
+          "kanton",
+          "adresse",
+          "status",
+          "letzte_meldung",
+          "profil"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+      ]
+    },
+    "neueste_verfuegbare_publikation": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "treffer_gesamt": {
+      "minimum": 0,
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "unvollstaendig_ab": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "weitere_treffer": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds the searchable keys and output fields but discloses no further operational behavior such as result limits or filter effects; that's acceptable given the annotation coverage.

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?

Three short sentences: what it does, what it returns, and when to use it. No filler or repetition; the core action is front-loaded.

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?

Annotations, output schema, and fully described parameters cover safety, return shape, and constraints. The description fills only the selection gap (name/UID lookup, use when UID unknown), which is exactly what an agent needs.

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 100%, with each parameter documented including the suchbegriff semantics. The description's phrase 'nach Name oder UID' reinforces suchbegriff but contributes little beyond the schema, so baseline 3.

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?

Opens with a specific verb and resource: 'Sucht Firmen im Schweizer Handelsregister nach Name oder UID'. It also states the returned fields and ends with a usage condition that separates it from UID-based siblings.

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 last sentence 'Nutze dies, wenn die UID nicht bekannt ist' gives clear when-to-use context. It doesn't name the alternative tools or state explicit when-not conditions, so it stops short of a 5.

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 tools Inspect

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

Need Help?