Skip to main content
Glama

Look up a Swiss UID

lookup_uid
Read-only

Retrieve Swiss federal UID register details for a company by UID or VAT number, including name, address, legal form, and VAT/commercial-register status after offline check-digit validation.

Instructions

Look up one entity in the federal UID register (BFS) by its UID, e.g. 'CHE-107.028.276', 'CHE107028276', '107028276' or a VAT number 'CHE-107.028.276 MWST'. Validates the check digit first (offline). Returns name, legal form, address, UID status, VAT register status (registered yes/no, VAT number, entry date) and commercial-register status. Covers ALL UID holders incl. associations, foundations, sole proprietors and public bodies that are not in ZEFIX.

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": "lookup_uid"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesUID in any format, e.g. 'CHE-107.028.276' or '107028276'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint, so the description must carry the rest — and it does, disclosing the offline check-digit validation (an early-failure, no-network behavior) and enumerating exactly what the response contains: name, legal form, address, UID status, VAT register status and commercial-register status. It does not say what happens when the check digit fails or the UID is unknown (error vs. empty result), which is the main remaining gap for a no-output-schema tool.

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 dense sentences with the operation and accepted formats front-loaded, followed by input validation behavior and return fields. Every sentence contributes: no restatement of the tool name, no 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?

For a single-parameter, read-only lookup with no output schema, the description covers purpose, input formats, validation behavior, return contents and dataset scope. The only shortfall is undefined behavior on invalid or unmatched identifiers, which an agent would want to know before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100% with a format example, so the baseline is 3. The description earns above baseline by adding a format the schema omits — a VAT number like 'CHE-107.028.276 MWST' — which materially changes how the agent may supply the parameter.

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?

States a specific verb and resource — looking up one entity in the federal UID register (BFS) by exact UID — and enumerates the accepted identifier forms. The phrase 'one entity' implicitly separates it from a broad register search, so an agent can tell it apart from search_uid_register without opening a 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 makes the use case clear: exact-identifier resolution, with the check digit validated offline before any lookup. It also scopes coverage ('ALL UID holders incl. associations, foundations, sole proprietors and public bodies that are not in ZEFIX'), which tells the agent when this tool still works. It stops short of explicitly naming search_uid_register as the alternative for partial-name queries.

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

Deploy Server

Other Tools