Skip to main content
Glama

Kalkulator B2B

Etat — z brutto na rękę

uop_from_gross
Read-only

Pełne rozliczenie umowy o pracę na cały rok: ZUS pracownika, składka zdrowotna, zaliczka PIT, PPK, netto miesiąc po miesiącu oraz koszt pracodawcy. Obsługuje ulgę dla młodych, prorodzinną, 4+, PIT-0 dla rodzin, koszty autorskie i ulgę na powrót. Liczy narastająco, więc pokazuje miesiąc przekroczenia progu skali.

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": {
      "monthlyGross": "<monthlyGross>",
      "year": "<year>"
    },
    "name": "uop_from_gross"
  }
}

Input Schema

NameRequiredDescriptionDefault
ppkNo
yearYesRok podatkowy — decyduje o stałych (progi, ZUS, płaca minimalna)
hasPIT2NoZłożony PIT-2 (kwota wolna dzielona na miesiące)
allowancesNo
monthlyGrossYesBrutto na kolejne miesiące. Jedna liczba = tyle samo przez cały rok
withSicknessNoSkładka chorobowa — na umowie o pracę obowiązkowa
costDeductionTypeNoKoszty uzyskania: local = miejscowe, non-local = dojazdowelocal

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/openWorldHint=false/destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: it computes cumulatively ('Liczy narastająco') and reports the month in which the tax-scale threshold is crossed, plus employer cost. It still omits defaults and the annual-only constraint implied by the maxItems=12 schema.

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?

Two dense sentences: the first front-loads what is computed, the second covers supported reliefs and the cumulative calculation behavior. No filler and no repetition of the title.

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 and a 7-parameter nested input, the description does the work of naming the return contents (net month-by-month plus employer cost) and the cumulative threshold behavior. It falls short only on assumptions an agent might need, such as default PIT-2/sickness handling and what happens with a partial-year gross array.

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 71%, so the schema already documents most parameters including the ppk and allowances sub-objects. The description adds value by enumerating which reliefs are supported (ulga dla młodych, prorodzinna, 4+, PIT-0, koszty autorskie, ulga na powrót), mapping them to the nested allowances object, but says nothing about the shape of monthlyGross beyond the schema's own 'jedna liczba = tyle samo' note.

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?

States a specific verb and scope: 'Pełne rozliczenie umowy o pracę na cały rok' with the enumerated components (ZUS, składka zdrowotna, zaliczka PIT, PPK, netto, koszt pracodawcy). It is clearly a gross-to-net annual payroll engine, distinguishable from aggregate tools like b2b_vs_uop, though it never names the nearest sibling uop_from_net to sharpen the contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the title 'z brutto na rękę' and the phrase 'na cały rok' — the agent must infer that this is the choice when the input is monthly gross rather than net. No explicit when-not or alternative is given, and nothing tells the agent to prefer uop_multi_year for multi-year horizons.

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