Skip to main content
Glama

Kalkulator B2B

Terminy ZUS, PIT i VAT

tax_deadlines
Read-only

Terminy płatności ZUS, zaliczki PIT (albo ryczałtu) i VAT, które przypadają w danym miesiącu, z przesunięciem z weekendu i święta na dzień roboczy. Dla jednoosobowej działalności, która płaci składki ZUS wyłącznie za siebie. Bez kwot — tylko daty i okresy, za które się płaci.

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>",
      "month": "<month>"
    },
    "name": "tax_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesRok podatkowy — decyduje o stałych (progi, ZUS, płaca minimalna)
monthYesMiesiąc, w którym przypadają płatności (1-12)
pitFrequencyNoZaliczki PIT (albo ryczałtu) miesięczne czy kwartalne; bez wartości — oba warianty
vatFrequencyNoVAT miesięczny, kwartalny albo EXEMPT (zwolniony z VAT); bez wartości — oba warianty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds genuine behavioral detail: weekend/holiday shifts to the next working day and the absence of monetary amounts. It does not disclose the shape of the returned deadlines or how many entries to expect, so the addition is useful but partial.

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 short sentences, front-loaded with what is returned, then the audience constraint, then the output-shape caveat. Every clause carries information; nothing 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?

For a read-only, no-output-schema tool with four well-documented parameters, the description covers purpose, audience, the holiday-shift rule, and the absence of amounts. The only gap is that it does not say what form the returned dates take (list, per-obligation breakdown), a minor omission given the explicit 'only dates and periods' note.

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 coverage is 100% and both enum parameters (pitFrequency, vatFrequency) already document their defaults ('no value — both variants'). The description adds no syntax or format meaning beyond the schema, so 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 names the concrete resource (ZUS/PIT/VAT payment deadlines falling in a given month) and narrows the audience to a sole proprietorship paying ZUS only for itself. It separates itself from data-oriented siblings by stating it returns 'no amounts — only dates and periods,' though it never names an alternative tool directly.

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 sets a clear usage scope: for one-person businesses paying ZUS solely for themselves, implying it is not appropriate if the user employs staff or pays ZUS for others. No sibling tool is named as an alternative, so the routing signal is contextual rather than explicit.

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