finwire.pl - Polish financial data

Social security (ZUS) of a sole proprietor in Poland

calc_zus_contributions

Read-onlyIdempotent

Monthly social security contributions (ZUS: pension, disability, sickness, accident, Labour Fund) of a sole proprietor (JDG) in Poland under each scheme: start relief (ulga na start), preferential ZUS and full ZUS, with the contribution base. The health contribution depends on the tax form and income; use calc_net_income with form b2b for it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calc_zus_contributions"
  }
}

Input Schema

Name	Required	Description	Default
`year`	No	Polish tax year; default the current one.

Output Schema

Name	Required	Description	Default
`url`	Yes
`asOf`	No
`data`	No
`title`	Yes
`source`	Yes
`docsUrl`	Yes
`license`	Yes
`summary`	Yes
`citation`	Yes
`datasetId`	Yes
`sourceUrl`	No
`truncated`	No
`serverDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: which schemes and contribution types are included, that the contribution base is returned, and that the health contribution is deliberately out of scope.

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 sentences, front-loaded with the core purpose and the enumeration of components, followed by the sibling handoff. Slightly dense parenthetical listing but nothing is wasted.

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?

An output schema exists, so return values needn't be explained, and the single parameter is fully documented. The remaining useful addition would be explicit contrast with calc_employer_cost, but for a read-only calculator the definition is essentially complete.

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?

Only one parameter (year) and schema coverage is 100%, with the schema itself stating the default is the current year. The description adds no further meaning about the year parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (monthly ZUS contributions of a sole proprietor in Poland) and enumerates the components covered (pension, disability, sickness, accident, Labour Fund) and the three schemes (ulga na start, preferential, full). It also explicitly bounds scope by excluding the health contribution, which separates it from calc_net_income.

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?

Gives a clear handoff rule: for the health contribution, use calc_net_income with form b2b. It does not, however, contrast with calc_employer_cost or compare_business_forms, both plausible neighbours for employment-cost questions, so the routing is only partially complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All finwire.pl - Polish financial data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.