Skip to main content
Glama

Kalkulator B2B

Etat — kilka lat

uop_multi_year
Read-only

Projekcja etatu na kilka lat z coroczną podwyżką, każdy rok z własnym narastaniem progu. Rok z opublikowanymi stałymi liczy się na własnych stałych podatkowych. Rok, na który rejestr nie ma jeszcze stałych, liczy się na stałych ostatniego opublikowanego roku i jest oznaczony gwiazdką jako założenie. Projekcji nie da się zacząć przed pierwszym rokiem rejestru.

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": {
      "startYear": "<startYear>",
      "years": "<years>",
      "initialGross": "<initialGross>"
    },
    "name": "uop_multi_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
ppkNo
yearsYes
hasPIT2NoZłożony PIT-2 (kwota wolna dzielona na miesiące)
startYearYesRok podatkowy — decyduje o stałych (progi, ZUS, płaca minimalna)
allowancesNo
initialGrossYesBrutto miesięcznie w pierwszym roku
withSicknessNoSkładka chorobowa — na umowie o pracę obowiązkowa
costDeductionTypeNoKoszty uzyskania: local = miejscowe, non-local = dojazdowelocal
annualRaisePercentNoPodwyżka rocznie, w procentach

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: per-year threshold accumulation, fallback to the last published tax constants with an asterisk marking it as an assumption, and the start-year limitation — all things an agent could not derive from annotations or 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?

The core purpose is front-loaded in the opening clause, followed by three short sentences that each carry a distinct rule. Slightly dense with domain jargon ("narastanie progu") but no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with nested allowance/PPK objects and no output schema, the description covers the projection logic and the asterisk return convention but leaves the optional parameter families (PPK contributions, allowance objects, cost deduction type) unaddressed. Adequate for the headline behavior, incomplete for the full surface.

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 67%, so the schema does most of the work. The description reinforces annualRaisePercent ("coroczną podwyżką") and adds registry-derived meaning to startYear beyond the schema's static min/max, but says nothing about initialGross, PPK settings, allowances, or the hasPIT2/withSickness defaults.

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?

"Projekcja etatu na kilka lat" gives a specific verb (projekcja) and resource (etat / employment contract) with an explicit multi-year scope, which separates it from the single-year siblings uop_from_gross and uop_from_net. It never names the B2B counterparts, so the differentiation rests on the reader inferring 'etat' = UoP.

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?

It states one hard precondition (the projection cannot start before the registry's first year) and explains how future years are handled, which tells the agent when the tool is applicable. However, there is no explicit routing guidance such as 'use uop_from_gross for a single year' or 'use b2b_multi_year for B2B', so the choice among siblings is left implicit.

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