Skip to main content
Glama

Kalkulator B2B

Etat — z netto na brutto

uop_from_net
Read-only

Szuka wynagrodzenia brutto, przy którym na rękę zostaje zadana kwota. Liczone iteracyjnie na stałych wskazanego miesiąca, z tymi samymi ulgami i PPK co pozostałe narzędzia etatowe.

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": {
      "targetNet": "<targetNet>",
      "year": "<year>",
      "month": "<month>"
    },
    "name": "uop_from_net"
  }
}

Input Schema

NameRequiredDescriptionDefault
ppkNo
yearYesRok podatkowy — decyduje o stałych (progi, ZUS, płaca minimalna)
monthYesMiesiąc 1-12
hasPIT2NoZłożony PIT-2 (kwota wolna dzielona na miesiące)
targetNetYesKwota na rękę, dla której szukamy brutto
allowancesNo
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.7/5.0
Behavior4/5

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

The annotations already establish the tool as a safe, closed-world read, and the description adds real behavioral detail beyond them: the result is computed iteratively on the constants of the indicated month ("Liczane iteracyjnie na stałych wskazanego miesiąca"), and it uses the same allowances and PPK treatment as the other employment tools, meaning results are consistent. It does not disclose precision or how non-convergence is handled, which is a modest gap for a numerical solver.

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 sentences, front-loaded with the purpose, followed by the computational caveat. No filler, and every clause carries information the agent needs to call the tool correctly.

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 an 8-parameter tool with nested objects and no output schema, the description covers the calculation method and the cross-tool consistency. It still omits what the tool actually returns (a single gross figure? a breakdown?) and how an unreachable targetNet is surfaced, which an agent needs for this complexity.

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?

At 75% schema coverage, the schema already documents most parameters (including year, month, PIT-2, and the nested allowance and PPK objects). The description adds the meaning that the calculation uses month-specific constants and mirrors the allowance and PPK semantics of the other employment tools, which helps with the nested objects. However, it adds no parameter-level syntax beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb and result: it searches for the gross salary that leaves the given net amount ("Szuka wynagrodzenia brutto, przy którym na rękę zostaje zadana kwota"). That inverts the forward calculation performed by uop_from_gross, so the agent can distinguish the two. It does not name that sibling directly, so the differentiation relies on inference rather than an explicit comparison.

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?

The use case (reverse net-to-gross calculation) is implied by the purpose statement, but there is no explicit guidance on when to choose this tool over uop_from_gross or the b2b equivalents. There is also no mention of preconditions, such as whether targetNet must be achievable or how a failure is reported.

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