Skip to main content
Glama

Search Swiss companies

search_companies
Read-only

Search the Swiss commercial register (ZEFIX) by company name or UID to retrieve legal form, seat, status, and cantonal register excerpt links. Filter results by canton and paginate large result sets.

Instructions

Search the Swiss commercial register (ZEFIX, 700k+ entities) by company name. Returns UID, legal form, seat, status and a link to the cantonal register excerpt. A UID like 'CHE-123.456.789' as query is looked up directly.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesCompany name (or UID) to search for
cantonNoOptional canton filter, e.g. 'ZH'
offsetNoPagination offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it enumerates the returned fields (UID, legal form, seat, status, cantonal register link) and discloses the special UID-as-query lookup behavior, which the annotations do not convey.

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 tight sentences with no filler: purpose first, return shape second, special input case last. Every sentence carries distinct information.

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?

There is no output schema, but the description compensates by listing returned fields, and the open-world read-only nature is covered by annotations. The remaining gap is pagination behavior (limit/offset) for a register with 700k+ entities, where an agent would want to know how to page results.

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 description coverage is 75%, with query, canton, and offset documented inline; only limit lacks a schema description. The description adds a genuine semantic point the schema omits — that the query string may be a UID like 'CHE-123.456.789' and is resolved directly — but says nothing about the canton filter or pagination interplay between limit and offset.

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 names a specific verb and resource — searching the Swiss commercial register (ZEFIX) by company name — and quantifies scope at 700k+ entities. It stops short of explicitly distinguishing itself from the closely named sibling search_uid_register, which an agent could easily confuse it with.

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 by the stated input (company name) plus the extra hint that a UID is looked up directly rather than fuzzy-matched. There is no explicit when-to-use or when-not guidance and no named alternative for the UID-lookup case, leaving routing to inference.

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