Skip to main content
Glama

Norman formation planner

German GmbH or UG formation plan

norman_de_company_formation
Read-onlyIdempotent

Plans the formation of a German GmbH or UG (haftungsbeschränkt) from the number of founders and the share capital, for someone who wants to know what forming the company involves and costs. Returns the legal form the capital allows (GmbH from 25,000 €, otherwise UG), whether the statutory Musterprotokoll fits (up to 3 founders, one managing director, no clauses of their own), the minimum deposit before the register application, the notary and commercial register fees as an estimated range (the notary's invoice under the GNotKG decides), the steps that follow, and continueInNorman, a link that opens Norman's formation chat with this plan filled in. Rules only: no account access, nothing is saved, and the result is general information, not legal or tax advice. The inputs hold no personal data: companyName is the planned company's name, and there are no fields for founders' names, birth dates, addresses or email.

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": {
      "country": "<country>",
      "year": "<year>",
      "founders": "<founders>",
      "shareCapital": "<shareCapital>"
    },
    "name": "norman_de_company_formation"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoRegistered office city (Sitz) in Germany.
ideaNoThe user's business idea in their own words.
yearYesYear of the rules and rates: 2026.
countryYes
foundersYesNumber of founders (shareholders); Norman supports up to 5.
companyNameNoPlanned name of the company, not a person's name.
shareCapitalYesShare capital in whole euros.
businessPurposeNoUnternehmensgegenstand: one concrete sentence on what the company does.
managingDirectorsNoNumber of managing directors; defaults to 1.
individualArticlesNoTrue when the founders want articles of their own instead of the statutory template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, closed-world, non-destructive call; the description adds genuinely new behavior: no account access, nothing persisted, output is general information rather than legal/tax advice, and fees are an estimated range because the GNotKG notary invoice governs. It also discloses the continueInNorman handoff link, which is non-obvious side-channel context an agent should surface to the user.

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?

Purpose and return values are front-loaded in the first sentences, then boundaries and privacy notes follow in a logical order with no filler. The closing privacy sentence is somewhat long-winded in enumerating absent fields, a minor cost against an otherwise dense paragraph.

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?

There is no output schema, and the description compensates by enumerating the returned items: the legal form the capital allows, Musterprotokoll eligibility, minimum deposit, fee range, next steps, and the continueInNorman link. For a 10-parameter, no-side-effect planning tool this leaves nothing an agent needs missing.

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 already 90%, so the baseline is 3; the description still adds meaning by clarifying that companyName is the planned company's name and by stating that no personal-data fields (founder names, birth dates, addresses, email) exist, which tells the agent it cannot collect those. It does not explain the 25,000 € threshold's interaction with shareCapital or what individualArticles changes, so it stops short of a 5.

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?

Opens with a specific verb and resource: 'Plans the formation of a German GmbH or UG (haftungsbeschränkt)', and names the two inputs that drive the plan (founders, share capital). The German jurisdiction plus the GmbH/UG scope distinguishes it from the Polish formation siblings without the agent needing to open any schema.

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?

Gives a clear use case ('someone who wants to know what forming the company involves and costs') and hard boundaries: rules only, no account access, nothing saved, not legal or tax advice. It does not explicitly say when to prefer a sibling or what to do if the user wants an already-existing company, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources