Skip to main content
Glama

Search the UID register by name

search_uid_register
Read-only

Find Swiss companies, associations, foundations and public administrations by name in the federal UID register (BFS); narrow by canton or postcode to get UID, legal form, address and VAT status.

Instructions

Search the federal UID register (BFS) by entity name; it covers every UID holder (companies, associations, foundations, sole proprietors, public administrations), not just commercial-register entries. Optionally narrow by canton ('ZH') or postcode ('8001'); these filters are applied to the returned candidates. Returns UID, name, legal form, address, VAT and commercial-register status. Example: name='Pro Natura', name='Gemeinde Köniz'.

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": {
      "name": "<name>"
    },
    "name": "search_uid_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesEntity name or fragment, e.g. 'Migros', 'Verein Pro Velo'
limitNo
cantonNoOptional canton filter, e.g. 'BE'
postcodeNoOptional Swiss postcode filter, e.g. '3001'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already establish readOnly and openWorld, so the safety profile is covered. The description adds one genuinely useful behavioral detail — that canton and postcode filters are applied to the returned candidates rather than acting as a pre-search restriction — plus the list of returned attributes. It says nothing about matching behavior (prefix vs. substring vs. fuzzy), result ordering, or truncation, which matter for a name-fragment search.

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 purpose and scope, then filters, then return fields — a sensible order with little waste. The trailing 'Example: name='Pro Natura', name='Gemeinde Köniz'.' is awkwardly labeled as a single example and is the one slack sentence.

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?

With no output schema, the description correctly enumerates what comes back (UID, name, legal form, address, VAT, commercial-register status), and the candidate-filter nuance is the key non-obvious behavior. Remaining gaps — matching semantics, limit behavior, pagination — are modest for a read-only lookup.

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 75%, so the schema carries most of the load, but the description adds real meaning: it gives concrete filter examples ('ZH', '8001') and, importantly, explains that these filters constrain the returned candidates. It does not mention the limit parameter or how name fragments are matched.

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?

Names a specific verb and resource ('search the federal UID register (BFS) by entity name') and immediately scopes coverage: every UID holder, not just commercial-register entries. That scope statement clearly separates it from register-specific siblings like search_companies.

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 coverage statement gives clear context for when this tool is the right choice ('not just commercial-register entries'), and the optional canton/postcode guidance signals the narrowing workflow. It stops short of explicitly naming an alternative such as a direct UID lookup for when the identifier is already known.

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