Skip to main content
Glama

search_companies

Read-onlyIdempotent

Find Swiss companies in the ZEFIX commercial register by full or partial name, with optional filters for canton and legal form to narrow results.

Instructions

Search the ZEFIX commercial register by company name, optionally filtered by canton/legal form

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_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull or partial name, min 3 chars; * is a wildcard
limitNo
cantonNoCanton of the registered seat
legal_formNoLegal form id, e.g. 3=AG, 4=GmbH (see list_legal_forms)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"Canton abbreviation (e.g. ZH, BE, GE, ZG)"New value: +"Canton of the registered seat"
    • addedInput schema / properties / canton / enum
      Added value: +[
      +  "AG",
      +  "AI",
      +  "AR",
      +  "BE",
      +  "BL",
      +  "BS",
      +  "FR",
      +  "GE",
      +  "GL",
      +  "GR",
      +  "JU",
      +  "LU",
      +  "NE",
      +  "NW",
      +  "OW",
      +  "SG",
      +  "SH",
      +  "SO",
      +  "SZ",
      +  "TG",
      +  "TI",
      +  "UR",
      +  "VD",
      +  "VS",
      +  "ZG",
      +  "ZH"
      +]
    • changedInput schema / properties / legal_form / description
      Previous value: -"Legal form code (e.g. 0106=GmbH, 0101=AG)"New value: +"Legal form id, e.g. 3=AG, 4=GmbH (see list_legal_forms)"
    • changedInput schema / properties / legal_form / type
      Previous value: -"string"New value: +"number"
    • addedInput schema / properties / limit / default
      Added value: +20
    • removedInput schema / properties / limit / description
      Removed value: -"Max results (default: 20)"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • changedInput schema / properties / name / description
      Previous value: -"Company name or partial name to search"New value: +"Full or partial name, min 3 chars; * is a wildcard"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behaviour, so the bar is lower. The description adds the data source (ZEFIX commercial register), but says nothing about result caps, ordering, substring vs. prefix matching semantics, or what happens when a filter combination yields no hits.

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?

One front-loaded sentence with no filler; the searchable resource and the optional filters appear in order of importance. The slash notation ('canton/legal form') is slightly compressed but readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 could have said what a result contains (e.g., company name, UID, seat, legal form) and whether results are truncated at the limit. For a simple read-only lookup tool this is adequate but leaves real gaps an agent would want filled.

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 75% and the name parameter already documents minimum length and the * wildcard. The description only confirms that canton and legal_form are optional filters applied alongside the name; the undocumented limit parameter (default 20, max 100) receives no explanation in either place.

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 — search the ZEFIX commercial register — plus the primary key (company name) and the optional filters. It implicitly separates itself from get_company (detail lookup) and search_companies_by_locality, though it never names them.

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: query by name when you know all or part of a company name. There is no explicit guidance on when to prefer get_company for details, search_companies_by_locality for location-based discovery, or list_legal_forms to resolve the legal_form id, so the agent must infer routing.

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