Skip to main content
Glama

List Swiss legal forms

list_legal_forms
Read-only

Retrieve the ZEFIX legal-form IDs used in the Swiss commercial register to map company legal forms such as AG, GmbH, and foundations.

Instructions

List the legal-form codes (ZEFIX legalFormId) used in the Swiss commercial register (AG, GmbH, foundation, …).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_legal_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that these are ZEFIX legalFormId codes drawn from the Swiss commercial register, but it says nothing about the returned shape (code-only versus code+label), ordering, or caching/stability of this reference data. Some added value beyond annotations, but not rich.

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?

A single sentence with zero waste, front-loading the resource, the identifier system (ZEFIX legalFormId), and illustrative examples. Every element earns its place.

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 zero-parameter reference-list tool with annotations covering the read-only profile, the description is nearly sufficient. The only real omission is the shape of the return value, which matters somewhat given there is no output schema.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the schema coverage is 100% and empty regardless.

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?

States a specific verb ('List') and a precise resource ('legal-form codes (ZEFIX legalFormId)') scoped to the Swiss commercial register, with concrete examples (AG, GmbH, foundation). It does not explicitly differentiate itself from sibling list_* tools, but the domain-specific vocabulary makes its subject unmistakable.

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?

No explicit when-to-use or when-not-to-use guidance and no named alternatives. The usage is only implied: an agent should call this when it needs to interpret or map legal-form codes appearing in commercial-register data. Adequate but leaves the routing to inference.

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