Skip to main content
Glama
whybothercoding

Zefix MCP Server

by whybothercoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_daily_registrations

Retrieve Swiss company registrations and SOGC publications for a specific date, then filter by canton or mutation type and page through results.

Instructions

Get company registrations and publications from SOGC (Swiss Official Gazette of Commerce) for a specific date using the Zefix API. A day has ~1,000 publications, so results are compact summaries; filter by canton and mutationType, page with offset, and set includeText for the full publication text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate in format YYYY-MM-DD
cantonNoOnly publications of this cantonal commercial registry (2-letter code, e.g. ZH)
offsetNoNumber of matching publications to skip, for paging (default: 0)
maxResultsNoMaximum number of publications to return (default: 50, max: 200)
includeTextNoInclude the full publication text (default: false; keep maxResults small when true)
mutationTypeNoOnly publications with this mutation type key, e.g. status.neu (new registration), status.loeschung (deletion), status.aufl (dissolution), adressaenderung, firmenaenderung (name change), kapitalaenderung, aenderungorgane (officers). A key also matches its sub-keys (status matches status.*).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it delivers substantial behavioral context: volume (~1,000 publications/day), that results are compact summaries by default, that includeText expands them, and the pagination model. It omits auth requirements and rate limits, so not a 5.

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?

Two dense sentences, front-loaded with the verb/resource/scope before the operational hints. Every clause (sources, volume, filters, paging, text flag) earns its place with no filler.

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?

For a 6-parameter read tool with no output schema and no annotations, the description covers volume expectations, default result shape, pagination, and the text toggle. It stops short of describing what the compact summary actually contains or how to page to exhaustion.

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 100%, so the baseline is 3, but the description adds a cross-parameter interaction the schema does not encode: keeping maxResults small when includeText is true. That extra guidance raises it above the schema-duplication baseline.

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 (get company registrations and publications), names the source (SOGC via the Zefix API), and scopes it to a specific date. The date-scoping distinguishes it from the per-company sibling get_company_publications without needing to open either schema.

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?

Gives clear operational context: filter by canton and mutationType, page with offset, and set includeText for full text. It does not explicitly state when to prefer this over siblings like get_company_publications or advanced_search, so it falls short of full when/when-not 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