Firmenwatch — Swiss Company Register

UID prüfen

uid_pruefen

Read-onlyIdempotent

Prüft eine Schweizer UID auf Format und Prüfziffer (Modulo 11 nach Spezifikation des Bundesamts für Statistik) und schlägt sie im Bestand nach. Nutze dies, bevor du eine UID in ein System übernimmst — Tippfehler werden so erkannt.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uid`	Yes	Zu prüfende UID

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`firma`	No
`grund`	No
`fehler`	No
`profil`	No
`status`	No
`gueltig`	No
`hinweis`	No
`quellen`	No
`datenstand`	No
`im_bestand`	No
`erlaeuterung`	No
`normalisiert`	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": [
+        "gueltig"
+      ]
+    }
+  ],
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "datenqualitaetsstatus": {
+      "enum": [
+        "current",
+        "processing",
+        "degraded",
+        "unavailable"
+      ],
+      "type": "string"
+    },
+    "datenstand": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "erlaeuterung": {
+      "type": "string"
+    },
+    "fehler": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "firma": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "grund": {
+      "type": "string"
+    },
+    "gueltig": {
+      "type": "boolean"
+    },
+    "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"
+    },
+    "im_bestand": {
+      "type": "boolean"
+    },
+    "lueckenlos_verifiziert_bis": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "neueste_verfuegbare_publikation": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "normalisiert": {
+      "type": "string"
+    },
+    "profil": {
+      "format": "uri",
+      "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"
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "unvollstaendig_ab": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

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

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description goes beyond these by disclosing the exact validation logic (Modulo 11 per BFS specification) and the lookup-against-registry behavior, which adds genuinely useful behavioral context.

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?

Two sentences with no filler. The first sentence leads with the core purpose and algorithm; the second provides a concrete usage recommendation. Every sentence earns its place.

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 tool with one well-documented parameter, strong annotations, and an output schema, the description covers what the tool does, how it validates, and when to use it. Nothing essential for selecting or invoking the tool correctly is missing.

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 100%: the single parameter 'uid' is described as 'Zu prüfende UID'. The description adds context about Swiss UIDs and validation, but does not add further parameter-level meaning. This matches the baseline for full schema coverage.

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 names a specific verb ('Prüft') and resource ('Schweizer UID'), and specifies the two concrete aspects being checked: format and check digit (Modulo 11). It also adds the registry lookup, making the tool's scope distinct from the sibling company-data tools without needing to open the schema.

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 states when to use the tool: before transferring a UID into a system, with the benefit that typos will be detected. It does not mention alternatives or when not to use it, but the context is clear enough for a single-purpose validation 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?