Firmenwatch — Swiss Company Register

Registerbefunde zu einer Firma

firma_risiko

Read-onlyIdempotent

Fasst zusammen, was im Handelsamtsblatt zu einer Firma publiziert wurde und geschäftlich relevant ist: Konkurs, Liquidation, Nachlassstundung, Kapitalherabsetzung und häufige Organwechsel. Jeder Befund ist einzeln benannt und datiert. Dies ist KEINE Bonitätsauskunft und bewertet KEINE natürlichen Personen.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uid`	Yes	UID der Firma

Output Schema

TableJSON Schema

Name	Required	Description	Default
`uid`	No
`code`	No
`firma`	No
`stufe`	No
`fehler`	No
`profil`	No
`befunde`	No
`hinweis`	No
`quellen`	No
`punktwert`	No
`datenstand`	No
`stufe_code`	No
`verfuegbar`	No
`einschraenkung`	No
`quellenhinweis`	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": [
+        "firma",
+        "uid",
+        "verfuegbar"
+      ]
+    }
+  ],
+  "properties": {
+    "befunde": {
+      "items": {
+        "properties": {
+          "befund": {
+            "type": "string"
+          },
+          "befund_code": {
+            "type": "string"
+          },
+          "erlaeuterung": {
+            "type": "string"
+          },
+          "gewicht": {
+            "type": "number"
+          },
+          "seit": {
+            "format": "date",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "befund_code",
+          "befund",
+          "gewicht",
+          "erlaeuterung",
+          "seit"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "code": {
+      "type": "string"
+    },
+    "datenqualitaetsstatus": {
+      "enum": [
+        "current",
+        "processing",
+        "degraded",
+        "unavailable"
+      ],
+      "type": "string"
+    },
+    "datenstand": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "einschraenkung": {
+      "type": "string"
+    },
+    "fehler": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "firma": {
+      "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"
+      ]
+    },
+    "neueste_verfuegbare_publikation": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "profil": {
+      "format": "uri",
+      "type": "string"
+    },
+    "punktwert": {
+      "type": "number"
+    },
+    "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"
+    },
+    "stufe": {
+      "type": "string"
+    },
+    "stufe_code": {
+      "enum": [
+        "keine",
+        "beobachten",
+        "erhoeht",
+        "kritisch"
+      ],
+      "type": "string"
+    },
+    "uid": {
+      "type": "string"
+    },
+    "unvollstaendig_ab": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verfuegbar": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 1, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: each finding is individually named and dated, and the results are filtered to business-relevant events.

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?

The description is compact and front-loaded: it states the core function first, gives concrete examples, then adds exclusions. Every sentence earns its place, and the clear negative statements help disambiguate without extra length.

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?

For a single-parameter read-only tool with a rich output schema and annotations covering safety, the description is complete. It explains what is summarized, what is included, and what is explicitly excluded, so an agent has enough context to invoke the tool correctly.

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?

There is only one parameter, uid, and the schema describes it as 'UID der Firma', giving 100% coverage. The description reinforces that the tool operates on a company but adds no meaningful new detail about the parameter format or syntax.

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 clearly specifies the verb ('Fasst zusammen'), the resource (Handelsamtsblatt publications about a company), and the relevant business topics such as bankruptcy, liquidation, and capital reduction. It does not explicitly differentiate from sibling tools by name, but it does state it is not a credit rating and does not assess natural persons, which narrows the scope.

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 gives clear context on what the tool covers and explicitly states when it should not be used: it is not a credit rating and does not assess natural persons. It does not name alternative sibling tools, but the negative guidance helps an agent avoid misusing the tool.

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?