Skip to main content
Glama

get_company

Retrieve comprehensive Swiss company details using its ZEFIX internal ID. Find the ID through company search to access official registration information.

Instructions

Get full details of a Swiss company by its ZEFIX internal ID (ehraid). Use search_companies first to find the ehraid — it is returned in company search results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ehraidYesCompany internal ZEFIX ID (ehraid integer, e.g. 119283). Returned by search_companies.

Implementation Reference

  • Handler logic for "get_company" tool that fetches company details using the ehraid.
    case "get_company": {
      // ZEFIX firm/{id}.json uses the internal ehraid integer (not CHE uid)
      const ehraid = args.ehraid as number;
      const url = `${BASE}/firm/${ehraid}.json`;
      const data = await fetchJSON<unknown>(url);
      return JSON.stringify(data, null, 2);
    }
  • Registration and input schema definition for "get_company" tool.
    {
      name: "get_company",
      description: "Get full details of a Swiss company by its ZEFIX internal ID (ehraid). Use search_companies first to find the ehraid — it is returned in company search results.",
      inputSchema: {
        type: "object",
        required: ["ehraid"],
        properties: {
          ehraid: { type: "number", description: "Company internal ZEFIX ID (ehraid integer, e.g. 119283). Returned by search_companies." },
        },
      },
    },
Behavior3/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. It indicates this is a read operation ('Get') and specifies the required input (ehraid), but doesn't disclose behavioral traits like rate limits, authentication needs, error conditions, or what 'full details' includes. The description adds some context but leaves important behavioral aspects unspecified.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second provides essential usage guidance. There's zero wasted language or 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?

For a single-parameter read tool with no annotations and no output schema, the description provides adequate purpose and usage guidance but lacks information about what 'full details' includes in the response, error handling, or any limitations. Given the simplicity of the tool, it's minimally complete but could benefit from more behavioral context.

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 the schema already fully documents the single parameter. The description adds minimal value beyond the schema by reinforcing that ehraid comes from search_companies and is an integer, but doesn't provide additional semantic context about the parameter's meaning or usage.

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 clearly states the tool's purpose: 'Get full details of a Swiss company by its ZEFIX internal ID (ehraid).' It specifies the verb ('Get'), resource ('Swiss company'), and unique identifier ('ZEFIX internal ID'), and distinguishes it from sibling 'search_companies' by indicating that tool should be used first to find the ehraid.

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?

The description explicitly provides usage guidance: 'Use search_companies first to find the ehraid — it is returned in company search results.' This tells the agent when to use this tool (after obtaining ehraid from search_companies) and names the alternative tool for initial searching.

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/vikramgorla/mcp-swiss'

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