Skip to main content
Glama

get_company

Read-onlyIdempotent

Retrieve full company details from the Swiss ZEFIX registry using an ehraid from search results. Returns official company data for verification or analysis.

Instructions

Full company details by ZEFIX ehraid (from search_companies)

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

Input Schema

NameRequiredDescriptionDefault
ehraidYese.g. 119283

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / ehraid / description
      Previous value: -"Company internal ZEFIX ID (ehraid integer, e.g. 119283). Returned by search_companies."New value: +"e.g. 119283"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the provenance detail that records come from the ZEFIX registry; it says nothing about error behavior for a missing ehraid or the granularity of the returned record, so the added context beyond annotations is modest.

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?

One short, front-loaded sentence fragment with no filler; the resource and lookup key lead. It is terse to the point of being telegraphed, but nothing is wasted.

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?

This is a simple one-parameter lookup with rich annotations and no output schema, so the description only needs to establish the key and the return concept, both of which it does ("Full company details"). The absence of any field-level detail on the returned record is a minor gap given the tool's low complexity.

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 coverage is 100% and the single parameter is documented with an example (119283), so the schema carries the burden. The description adds the useful clarification that the value is a ZEFIX ehraid obtained from search_companies, which is meaning beyond a bare numeric example, but no format or validity constraints.

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 names a specific resource (company), a specific identifier (ZEFIX ehraid), and the scope (full details), and it points back to search_companies as the source of that identifier. It is clearly distinguishable from search_companies and search_companies_by_locality, though it never enumerates which company fields are returned.

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

Usage Guidelines3/5

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

The parenthetical "(from search_companies)" implies the workflow: get an ehraid from search_companies, then call this tool to resolve it to full details. That is useful implied guidance, but there is no explicit when-to-use/when-not-to-use statement and no mention of what to do if the ehraid is unknown or which sibling to use for name or locality searches.

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