Skip to main content
Glama

Norman formation planner

Polish spółka z o.o. formation plan

norman_pl_spzoo_formation
Read-onlyIdempotent

Plans the formation of a Polish spółka z o.o. from the number of shareholders and the share capital (from 5,000 zł, paid in full), for someone who wants to know the routes, costs and deadlines. Returns the S24 route next to a notarial deed (court fee 250 zł or 500 zł, PCC at 0.5% of the capital less the court fee; the notary's own fee is not estimated), the deadlines after the KRS entry (capital, PCC-3, ZUS, CRBR, NIP-8, VAT-R), CIT figures on one example profit, and continueInNorman, a link that opens Norman's sp. z o.o. planner with this plan. The founders sign and file in S24 or at a notary themselves; the tool files nothing and checks no company name. Rules only: nothing is saved, and the result is general information without a recommendation of a tax form, CIT rate or ZUS scheme, not legal or tax advice. The inputs hold no personal data: there are no fields for names, PESEL, NIP, 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_pl_spzoo_formation"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoRegistered office city (siedziba) in Poland.
ideaNoThe user's business idea in their own words.
yearYesYear of the rules and rates: 2026.
countryYes
foundersYesNumber of shareholders; Norman's planner supports up to 5.
companyNameNoPlanned name of the company, not a person's name.
shareCapitalYesShare capital in whole złoty, at least 5,000.
businessPurposeNoWhat the company will do, in one concrete sentence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint/idempotentHint, it discloses the actual output shape (S24 vs notarial deed, 250/500 zł court fee, PCC 0.5% less court fee, post-KRS deadlines, CIT on one example profit, a continueInNorman link) and, importantly, what it does NOT do: no filing, no company-name check, nothing saved, no notary fee estimate, no legal/tax advice. That is exactly the negative-space disclosure annotations cannot carry.

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?

Front-loaded with purpose and cost outputs, then boundaries and disclaimers, so a reader can stop early. It is a single dense paragraph with some redundancy ("nothing is saved" and "Rules only" overlap; the no-personal-data sentence repeats the absence of name/NIP fields).

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?

With no output schema, the description carries the return-value burden well by enumerating the plan's sections and the continueInNorman handoff. Minor gaps remain: the fixed country=PL and year=2026 constants and the 5-shareholder cap are not explained, though the schema consts make them self-evident.

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 already 88%, so parameter documentation is largely handled. The description reinforces the founders and shareCapital semantics (minimum 5,000 zł, paid in full) and notes that no personal-data fields exist, but adds little on the optional city/idea/companyName/businessPurpose parameters. Baseline 3 is appropriate.

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?

"Plans the formation of a Polish spółka z o.o." is a specific verb plus resource, and the qualifier (number of shareholders, share capital from 5,000 zł paid in full) scopes it precisely. The Polish sp. z o.o. framing separates it from the JDG and German formation siblings without needing to name them.

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?

"for someone who wants to know the routes, costs and deadlines" gives a clear use context, and the closing note that the founders sign and file themselves clarifies the boundary of the tool's role. It stops short of explicitly naming when to prefer a sibling (e.g. JDG vs sp. z o.o.), so no exclusions are stated.

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