Skip to main content
Glama

Cash-service.pl

B2B vs umowa o pracę

kalkulator_b2b
Read-onlyIdempotent

Porównuje zarobki na etacie (UoP) i na własnej działalności (B2B) w Polsce: netto miesięcznie, składki ZUS, zdrowotna, podatek, koszty firmy, próg faktury równoważnej. Używaj do pytań „ile fakturować na B2B, żeby mieć tyle co na etacie", „czy B2B się opłaca przy X zł".

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": {
      "kwota": "<kwota>"
    },
    "name": "kalkulator_b2b"
  }
}

Input Schema

NameRequiredDescriptionDefault
rokNoRok (domyślnie bieżący)
zusNopelny = pełny ZUS, maly = preferencyjny (24 mies.), ulga = ulga na start (6 mies.)pelny
trybNoTryb obliczenia: miesiac (jedna forma), porownanie (cztery formy obok siebie), rozliczenie (roczne rozliczenie składki)brutto_uop
kwotaYesKwota miesięczna w PLN: brutto na etacie (tryb brutto_uop) albo faktura netto B2B (tryb faktura_b2b)
kosztyNoKoszty firmy PLN/mies. (bez księgowości)
chorobowaNoDobrowolna składka chorobowa na B2B
ksiegowoscNoKoszt księgowości PLN/mies.
opodatkowanieNoForma opodatkowania B2Bliniowy
stawka_ryczaltuNoStawka ryczałtu jako ułamek, np. 0.12 (tylko dla ryczałtu)
kup_autorskie_pctNoUdział honorarium autorskiego na etacie (0–1), 50 % KUP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered and the description only needs to add domain context — which it does by scoping the calculation to Poland and naming the components produced. It does not disclose assumptions or limitations (tax year rules, what is excluded from koszty firmy, whether the 'próg faktury równoważnej' is always returned), which matters for a financial calculator with no output schema.

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?

Two sentences, front-loaded with the purpose, followed by the usage trigger — no filler. The component list is dense but each item maps to a real computed output, so it earns its space.

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 10-parameter, read-only calculator with a fully documented schema and no output schema, the description gives an agent enough to select it and to know roughly what comes back (netto, składki, podatek, koszty, próg równoważny). A note on which tax-year rules or assumptions apply would close the remaining gap.

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 description coverage is 100% and the enums are self-documented, so the baseline is 3. The description adds no parameter-level meaning beyond the schema; the one term it introduces ('próg faktury równoważnej') is an output concept, not a parameter.

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 opens with a specific verb and resource ('Porównuje zarobki na etacie (UoP) i na własnej działalności (B2B) w Polsce') and then enumerates exactly what is computed: netto miesięcznie, ZUS, zdrowotna, podatek, koszty firmy, próg faktury równoważnej. That is far more specific than a restatement of the title. It doesn't explicitly distinguish itself from look-alike siblings such as kalkulator_plac or kalkulator_dzielo, which keeps it at 4.

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 second sentence gives concrete triggering questions ('ile fakturować na B2B, żeby mieć tyle co na etacie', 'czy B2B się opłaca przy X zł'), which is real when-to-use guidance an agent can pattern-match. There is no when-not guidance and no explicit pointer to the sibling calculators for pure-UoP or mandate-contract cases.

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