Skip to main content
Glama

list_legal_forms

Read-onlyIdempotent

Retrieve legal form IDs for Swiss companies, such as AG and GmbH, to use when searching companies.

Instructions

List company legal forms (AG, GmbH, ...) with the ids used by search_companies

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 observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context by explaining what the returned ids are for (input to search_companies). It does not describe ordering or whether the list is exhaustive, which is a minor remaining gap for a static lookup.

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 no filler, front-loaded with the resource and immediately followed by the examples and the downstream use of the ids. Every clause 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 enumeration with no output schema, the description conveys both what is returned (legal forms with ids) and why it matters (search_companies filtering). Only minor details such as ordering or result size are absent, which an agent is unlikely to need in order to call it.

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 zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No parameter-level guidance is needed or missing.

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 (list) and resource (company legal forms), gives concrete examples (AG, GmbH), and explains the value of the returned ids by tying them to search_companies. An agent can immediately distinguish this enumeration tool from search_companies and get_company.

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?

The phrase 'with the ids used by search_companies' signals the intended workflow: fetch this list to obtain legal-form ids for filtering company searches. It stops short of an explicit 'call this before search_companies when you need a legal-form filter', so it is clear context rather than a full when/when-not rule set.

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