Skip to main content
Glama

Get company details

get_company
Read-only

Retrieve a Swiss company's full ZEFIX record by UID, exact registered name, or EHRAID to view its purpose, seat, status, legal form, SOGC date, and register links.

Instructions

Full ZEFIX record for one company: purpose, translations, seat, status, legal form, SOGC date and register links. Identify the company by UID ('CHE-107.028.276' or its 9 digits), exact registered name (case-insensitive; otherwise candidates are returned), or numeric EHRAID.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesCompany UID (CHE-…), exact registered name, or numeric EHRAID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful behavior beyond those annotations: it lists the returned record fields and discloses the case-insensitive name matching with candidate fallback when no exact match is found.

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?

The description is two tightly written sentences with no wasted wording. The core record content is front-loaded, followed by the identifier rules and fallback behavior.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup tool, the definition is complete: it identifies the resource, lists the returned fields, covers all accepted identifier formats, and explains the non-exact-name fallback. The annotations already cover the safety profile, and no output schema is needed because the description enumerates the expected record contents.

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 schema already documents the single identifier parameter. The description still adds meaning by providing a concrete UID example, accepting a 9-digit UID form, stating case-insensitive name matching, and explaining the candidate fallback behavior.

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?

The description names a specific retrieval operation and resource: the full ZEFIX record for one company. It further specifies exactly which fields are returned and how the company can be identified, so an agent can distinguish this tool from sibling get_* tools for other datasets.

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?

It gives clear guidance on acceptable identifiers and explains that an exact registered name is required, with candidates returned otherwise. It does not explicitly name alternatives or when not to use the tool, but the context is sufficiently clear for a single-company lookup.

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