Skip to main content
Glama
ishumilin

Zefix MCP Server

by ishumilin

search_companies

Search for Swiss companies in the commercial register using filters for name, canton, legal form, and active status. Find registered entities with precise criteria.

Instructions

Search for Swiss companies using the Zefix API. Supports filtering by name, canton, legal form, and active status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCompany name to search for (minimum 3 characters, use * for wildcard)
cantonNo2-letter canton code (e.g., ZH, BE, GE)
activeOnlyNoOnly return active companies (default: true)
legalFormUidNoLegal form code (e.g., 0106 for AG, 0107 for GmbH)
maxResultsNoMaximum number of results to return (default: 30, max: 200)
Behavior3/5

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

No annotations exist, so description carries full burden. It mentions the API and filtering but omits details like response format, pagination behavior, rate limits, or authentication. Adequate but not comprehensive.

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?

Extremely concise single sentence (16 words) that front-loads the purpose. Every word earns its place without redundancy.

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?

Given 5 parameters, no output schema, and no annotations, the description could cover response format, default behavior, or error handling. It mentions filters but lacks completeness for a search tool.

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 100%, so baseline is 3. The description lists filter types (name, canton, etc.) but adds no additional meaning beyond what the schema already provides for each parameter.

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 clearly states the tool's purpose: searching for Swiss companies with filters. It names the Zefix API and lists supported filters, but does not explicitly differentiate from sibling tools like advanced_search.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., advanced_search, get_company_by_uid). Missing context on prerequisites or exclusions, leaving the agent to infer usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ishumilin/schwaizer-zefix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server