Skip to main content
Glama

Search Swiss companies

search_companies
Read-onlyIdempotent

Search the Swiss commercial register (Zefix) by company name and receive bounded, deduplicated candidate summaries (UID, legal name, legal form, register status, seat, canton) with source attribution. Use this to find a company's UID before calling get_company_profile, or to review candidates after verify_business reports an ambiguous name. Discovery only: no candidate is selected automatically, results are not ranked or scored, and a name match is not a verification result. For direct one-call verification, use verify_business.

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
nameYesCompany name to search for. Trimmed; 3–300 characters. Do not guess spellings; use the name as claimed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds real behavioral context: results are bounded and deduplicated, carry source attribution, are not ranked or scored, and no candidate is auto-selected. Since there is no output schema, the disclosed return fields are especially valuable. It stops short of stating any result cap or pagination behavior, leaving 'bounded' undefined.

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-loads the action and return shape, then usage, then the discovery-only caveat, then the sibling alternative, so the structure mirrors how an agent would read it. The parenthetical field list is efficient rather than wasteful; a few clauses, such as 'results are not ranked or scored', could be merged into a single caveat 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 and no annotations describing returns, the description compensates well by naming the summary fields and clarifying that a match is not a verification. The remaining gap is operational scale: how many candidates are returned and what happens with very common names is not addressed.

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?

Only one parameter exists and schema description coverage is 100%, including length bounds and the 'do not guess spellings' guidance. The description adds only 'by company name', which the schema already states, so the baseline of 3 applies.

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 (search the Swiss commercial register / Zefix by company name) and enumerates the returned fields, so the agent knows exactly what it gets back. It also explicitly distinguishes itself from both siblings, get_company_profile (downstream) and verify_business (the verification alternative), making selection unambiguous.

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

Usage Guidelines5/5

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

Gives explicit when-to-use cases: finding a UID before calling get_company_profile, or reviewing candidates after verify_business reports an ambiguous name. It also names the exclusion condition and the alternative, stating that for direct one-call verification the agent should use verify_business instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources