Skip to main content
Glama

Kalkulator B2B

Limit zwolnienia z VAT

vat_exemption_limit
Read-only

Limit sprzedaży dla zwolnienia podmiotowego z VAT (art. 113) na dany rok — pełny albo proporcjonalny do dni działalności dla firmy otwartej w trakcie roku (art. 113 ust. 9). Z podaną sprzedażą netto od 1 stycznia: ile zostało, jaki to procent limitu i poziom ostrzeżenia, a z dniem stanu (asOf) — ile średnio dziennie można jeszcze sprzedać do końca roku. Liczy wyłącznie z podanych liczb, bez prognozy. Mówi też, kto zwolnienia nie ma bez względu na sprzedaż (art. 113 ust. 13: m.in. usługi prawnicze i doradztwo). Lata tylko z opublikowanymi stałymi.

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

Input Schema

NameRequiredDescriptionDefault
asOfNoDzień, na który podajesz salesSoFar (RRRR-MM-DD, w tym samym roku). Wymaga salesSoFar; z nim narzędzie mówi też, ile średnio dziennie można jeszcze sprzedać do 31 grudnia
yearYesRok podatkowy — decyduje o stałych (progi, ZUS, płaca minimalna)
salesSoFarNoWartość sprzedaży NETTO (bez VAT) od 1 stycznia, liczona do limitu, w złotych
businessStartDateNoDzień rozpoczęcia działalności (sprzedaży), RRRR-MM-DD. Firma, która ruszyła w tym roku, ma limit proporcjonalny do dni działalności (art. 113 ust. 9). Bez daty — pełny limit roczny, jak dla firmy działającej od początku roku: zapytaj, gdy firma może być nowa

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: results derive strictly from supplied numbers with no projection ('Liczy wyłącznie z podanych liczb, bez prognozy'), and it flags the art. 113 ust. 13 category of entities excluded regardless of sales.

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 legal basis and output shape are front-loaded in the first sentence, and each subsequent sentence adds a distinct fact (asOf behavior, no-forecast rule, excluded professions, year limitation). The dense single-paragraph Polish phrasing is serviceable but would scan faster with clear separation of input modes.

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 carries the return-value burden and does so: remaining amount, percentage of limit, warning level, and daily average when asOf is supplied. The year constraint is also enforced in the schema, and the behavioral caveats are covered. Only the exact warnings thresholds are left implicit.

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%, so the schema already explains year, salesSoFar, asOf and businessStartDate. The description's notes about asOf producing a daily average and about the Jan 1 sales basis largely restate the schema, so 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?

The description names a concrete legal computation (art. 113 VAT subjective exemption limit) and specifies both variants: full-year and day-proportional for a business opened mid-year (art. 113 ust. 9). An agent can tell this is a limit calculator, not a generic constants lookup like tax_constants. It stops short of naming an alternative sibling to steer away from, so it lands at 4 rather than 5.

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 states the triggering scenarios clearly: with net sales from Jan 1 you get remaining amount, percentage and warning level; with asOf you also get the average daily allowance to year-end. It also adds a pre-condition ('Lata tylko z opublikowanymi stałymi') that tells the agent when the tool cannot answer. No explicit when-not or named alternative is given.

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