Skip to main content
Glama

ch_uid

Validate Swiss UID/VAT numbers against the official UID register, returning format checks, register status, legal name, address, and VAT status.

Instructions

Swiss UID / VAT (MWST/TVA/IVA) number validation against the official Swiss Federal Statistical Office UID register (UID-Register, uid-wse). Returns format check (mod-11), register status, legal name, legal form, address, commercial-register and VAT status. Sole-proprietor names are masked. Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "<uid>"
    },
    "name": "ch_uid"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesSwiss UID, e.g. CHE-105.829.940 or CHE105829940 MWST

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the validation method (mod-11 format check plus register lookup), the returned signals (register status, legal name, legal form, address, commercial-register and VAT status), a privacy behavior (sole-proprietor names masked), and the cost/auth model. The 402-without-key behavior is exactly the kind of operational detail an agent needs before calling.

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?

Front-loaded with what the tool validates and against which register, then compressed into a single dense sentence listing return fields, followed by the masking note and the payment terms. Every element earns its place; the only mild cost is that the return-field list reads as a run-on enumeration.

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?

No output schema exists, yet the description enumerates the meaningful return fields so an agent knows what it gets. Combined with the payment/401-style 402 disclosure and the masking caveat, nothing material is missing for a single-parameter validation tool.

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% and the schema already supplies the 'CHE-105.829.940' example, so the single parameter is well documented structurally. The description adds the semantic that the value is checked with a mod-11 checksum and that MWST/TVA/IVA suffixes appear in the acceptable form, but little beyond that. Baseline 3 applies.

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?

States a specific verb and resource: validation of Swiss UID / VAT (MWST/TVA/IVA) numbers against the official Federal Statistical Office UID register. The scope is unambiguous and the singular nature of the tool is clear from the description versus the 'ch_uid_batch' child name, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied: it validates one UID and returns register data. The description usefully states the payment precondition (0.003 USDC on Base via x402, 402 challenge without a key), which is a real gating condition. However, it never says when to prefer the likely alternative (ch_uid_batch for multiple numbers) or what happens on the failure side beyond the 402 case.

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