Skip to main content
Glama

Kalkulator B2B

IKZE — ile podatku oszczędza wpłata

ikze_benefit
Read-only

Limit wpłat na IKZE w roku i ile podatku oszczędza wpłata przy podanym przychodzie i kosztach JDG: PIT za rok bez wpłaty i z wpłatą, z tego samego silnika roku (różnica to oszczędność), co odliczenie obniża w danej formie (skala i liniowy — dochód, ryczałt — przychód), podatek od wypłaty na emeryturze i limit IKE dla porównania. Wpłata ponad limit jest wskazana wprost i liczona do limitu. selfEmployed trzeba podać — limit zależy od osoby, nie od firmy. Lata tylko z opublikowanymi stałymi.

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": {
      "monthlyRevenues": "<monthlyRevenues>",
      "monthlyCosts": "<monthlyCosts>",
      "taxForm": "<taxForm>",
      "zusVariant": "<zusVariant>",
      "isVatPayer": "<isVatPayer>",
      "year": "<year>",
      "contribution": "<contribution>",
      "selfEmployed": "<selfEmployed>"
    },
    "name": "ikze_benefit"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesRok podatkowy — decyduje o stałych (progi, ZUS, płaca minimalna)
taxFormYesLINIOWY = 19%, SKALA = 12/32%, RYCZALT = od przychodu
isVatPayerYestrue = czynny podatnik VAT, false = zwolniony z VAT
zusVariantYesBRAK = ulga na start — narzędzie liczy cały rok bez składek społecznych (ulga trwa 6 miesięcy; rok po niej policz z PREFERENCYJNY albo DUZY_ZUS), PREFERENCYJNY = mały ZUS (30% podstawy), DUZY_ZUS = pełny, UOP = etat obok działalności (społeczne po stronie pracodawcy)
ryczaltRateNoStawka ryczałtu w procentach. WYMAGANA dla RYCZALT — silnik jej nie zgaduje
contributionYesPlanowana wpłata na IKZE w tym roku, w złotych. "LIMIT" = wpłata całego limitu roku
monthlyCostsYesKoszty uzyskania przychodu NETTO na kolejne miesiące, tak samo rozciągane ([0] = bez kosztów). Zwolniony z VAT podaje je razem z VAT-em — nie odlicza go, więc VAT jest u niego kosztem
selfEmployedYesCzy oszczędzający prowadzi pozarolniczą działalność (art. 8 ust. 6 ustawy o systemie ubezpieczeń społecznych) — wtedy ma wyższy limit IKZE (art. 13a ust. 1a ustawy o IKE i IKZE). Właściciel JDG: true. Wymagane, bez wartości domyślnej: limit przysługuje osobie w danym roku, nie wynika z formy opodatkowania
monthlyRevenuesYesPrzychód netto na kolejne miesiące roku. Jedna liczba = tyle samo co miesiąc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, so safety is covered; the description adds real behavioral detail beyond that — contributions above the limit are flagged explicitly and capped, and all figures come from one consistent year engine so the difference is a genuine saving. It stops short of saying what happens on unsupported years beyond the 2024–2030 schema bound.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core output is front-loaded in the opening clause, but the body is one long semicolon-chained sentence that mixes purpose, calculation rules, parameter rationale and output composition. Some clauses duplicate what the schema already documents, so density comes at the cost of scannability.

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 nine parameters, all required except ryczaltRate, and no output schema, the description carries the return-value burden and does describe what comes back: PIT without and with the contribution, their difference as the saving, deduction base per form, payout tax at retirement, and the IKE limit for comparison. That is close to sufficient, with only edge-case behavior for unsupported years left implicit.

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%, so every parameter including zusVariant, selfEmployed and contribution already carries its own explanation. The description restates the selfEmployed rationale and the tax-form deduction base (skala/liniowy reduce income, ryczałt reduces revenue), which reinforces but does not materially extend the schema — the correct baseline for full coverage.

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?

The description names a specific compound deliverable: the annual IKZE contribution limit plus the tax saved by a contribution at a given revenue/cost profile, with PIT computed both without and with the contribution. It also enumerates secondary outputs (deduction base by tax form, retirement payout tax, IKE limit for comparison), which lets an agent separate it from generic B2B calculators in the sibling list.

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?

It states concrete preconditions: selfEmployed must be supplied because the limit attaches to the person not the business, and only years with published constants are valid. It does not explicitly name an alternative tool or say when not to use it (e.g. compared to b2b_compare_forms or b2b_year), so routing is implied rather than spelled out.

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