Skip to main content
Glama

Kalkulator B2B

JDG — rozliczenie straty

b2b_loss_relief
Read-only

Rozlicza stratę z lat ubiegłych według art. 9 ust. 3 ustawy o PIT: jednorazowo do 5 mln zł, reszta przez pięć lat po najwyżej połowie rocznie. Ryczałt strat nie przenosi i narzędzie mówi to wprost.

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": {
      "taxForm": "<taxForm>",
      "years": "<years>"
    },
    "name": "b2b_loss_relief"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYes
taxFormYesLINIOWY = 19%, SKALA = 12/32%, RYCZALT = od przychodu

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?

Annotations already declare a safe, closed, read-only computation, so the lower bar applies; the description still adds substantive behavior by disclosing the actual rule applied (up to 5 mln PLN one-time, remainder over five years at max half per year). That tells the agent what the tool will compute and where the caps bind, which is genuine context beyond the annotations.

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 tightly packed sentences, front-loaded with the governing rule and followed by the single exception that matters. Nothing is redundant and no sentence could be removed without losing substantive content.

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?

Annotations cover the safety profile, but with no output schema the description should say what comes back (e.g. deductible amount per year, remaining loss balance) and it does not. For a read-only two-parameter calculator the input side is adequately covered, so this is a moderate gap rather than a blocking one.

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?

With 50% schema description coverage, the enum for taxForm is already explained in the schema (LINIOWY 19%, SKALA 12/32%, RYCZALT) and income is documented as negative-means-loss. The description adds no per-parameter meaning, though the ryczałt remark indirectly signals that taxForm=RYCZALT yields a different outcome; baseline 3 is appropriate.

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 resource ('Rozlicza stratę z lat ubiegłych') and anchors it to a legal basis (art. 9 ust. 3 ustawy o PIT), so the agent knows exactly what is computed. It does not name or distinguish itself from plausible siblings such as b2b_multi_year or b2b_year, which keeps it below a 5.

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: the description makes clear it handles carry-forward of prior-year losses, and it rules out ryczałt losses ('Ryczałt strat nie przenosi'), which is a partial when-not signal. There is no explicit statement of when to call this instead of the multi-year or yearly calculation siblings, so the agent must infer the boundary.

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