Skip to main content
Glama

Cash-service.pl

Kalkulator płac brutto/netto (umowa o pracę, Polska)

kalkulator_plac
Read-onlyIdempotent

Liczy wynagrodzenie netto z brutto albo brutto z netto dla umowy o pracę w Polsce wg aktualnych stawek ZUS, składki zdrowotnej i PIT (silnik cash-service.pl, dane roczne 2024–2027). Zwraca składki, zaliczkę PIT, koszt pracodawcy. Używaj do pytań typu „ile na rękę z X brutto", „ile brutto, żeby mieć Y netto".

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_plac"
  }
}

Input Schema

NameRequiredDescriptionDefault
ppkNoUczestnik PPK (2 % pracownik)
rokNoRok podatkowy (domyślnie bieżący)
kwotaYesKwota miesięczna w PLN (brutto albo netto zależnie od kierunku)
kierunekNobrutto_netto = podaję brutto, chcę netto; netto_brutto = odwrotniebrutto_netto
koszty_uzyskaniaNoKoszty uzyskania: podstawowe 250 zł, podwyższone 300 zł (dojeżdżający), zeropodstawowe
symulacja_rocznaNoDodaj symulację 12 miesięcy z progami (120 000 zł, 30-krotność, ulga dla młodych)
ulga_dla_mlodychNoPIT-0 dla osób do 26. roku życia
pracownicze_koszty_autorskieNo50 % koszty autorskie (twórcy)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds real context beyond that: the computation engine (cash-service.pl) and the tax-year data coverage (2024–2027), which tells the agent how authoritative and current the result is. It does not mention rounding or precision, but nothing material is missing for a pure calculator.

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?

Three tight sentences: what it computes and under which regime, what it returns, and when to reach for it. The capability statement is front-loaded and no sentence is redundant.

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 correctly steps in to enumerate the returned values, and the schema carries all eight parameters with defaults. The only gap is that it does not explain what the 'symulacja_roczna' mode produces or how the annual thresholds surface in the response, which an agent might want to set expectations for.

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 every parameter carries its own Polish explanation, including the enum semantics for 'kierunek' and 'koszty_uzyskania'. The description only restates the bidirectional direction already documented in the schema, so it adds no meaning beyond structured fields — the baseline 3 applies.

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 states a specific verb and resource (calculates net from gross or gross from net) and scopes it precisely to 'umowa o pracę w Polsce', which separates it from the B2B, zlecenie and dzieło calculator siblings. It also names the outputs (składki, PIT advance, employer cost), so an agent knows exactly what the tool produces.

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 gives concrete trigger phrasings ('ile na rękę z X brutto', 'ile brutto, żeby mieć Y netto'), which is stronger than generic 'use for payroll questions'. However, it never names an alternative or an exclusion — an agent must infer on its own that a B2B or zlecenie question belongs to a different calculator.

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