Skip to main content
Glama

Kalkulator B2B

Stałe podatkowe

tax_constants
Read-only

Obowiązujące stałe na dany miesiąc: płaca minimalna i przeciętna, stawki ZUS, składka zdrowotna, próg skali, kwota wolna, danina solidarnościowa. Z rejestru stałych — użyj tego zamiast liczb z pamięci.

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_constants"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesRok podatkowy — decyduje o stałych (progi, ZUS, płaca minimalna)
monthYesMiesiąc 1-12

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 the safety profile is fully covered. The description adds that values come from an authoritative constants registry, which is useful provenance, but says nothing about return shape, precision, or whether values are annual vs monthly.

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?

Two compact sentences: the payload is front-loaded as a list, then the sourcing/usage directive. The enumeration is long but each item earns its place by telling the agent which constants are available. No filler wording.

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 only two required, fully documented parameters and no output schema, the description usefully compensates by listing the returned constants, which is exactly what an agent needs to judge relevance. No output schema means the enumerated field list carries the return-value burden adequately, though precision/units remain unstated.

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%, and the schema already explains that year selects the constants (thresholds, ZUS, minimum wage) and that month is 1-12. The phrase 'na dany miesiąc' only implies the month parameter and adds no syntax or edge-case meaning beyond the schema, 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 concretely enumerates what the tool returns (minimum/average wage, ZUS rates, health contribution, tax scale threshold, tax-free amount, solidarity levy), which is far more specific than the title 'Stałe podatkowe'. It never names a sibling or explicitly contrasts itself, but the enumerated payload makes it distinguishable from e.g. tax_deadlines or the calculators.

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?

'Z rejestru stałych — użyj tego zamiast liczb z pamięci' gives an explicit directive about when to reach for this tool (whenever a constant value is needed, never from memory). It stops short of naming alternatives or stating exclusions, so it is clear context rather than full when/when-not guidance.

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