finwire.pl - Polish financial data

Next-year statutory limits from legal formulas

get_next_year_limits

Read-onlyIdempotent

Statutory values for the next year computed by finwire.pl from the formulas in Polish law on the latest GUS and NBP data, before the official act (finwire_next_year_limits): pension indexation and minimum pension, minimum wage and hourly rate (statutory minimum rise), projected average wage, IKE and IKZE limits, the 30x ZUS cap, ZUS contribution bases, flat-rate tax and small CIT taxpayer limits. Each item: value, 80% interval, stage (projekcja = estimate, projekt, obwieszczenie = announced, obowiazuje = in force), calculation and backtest accuracy. Present estimates as estimates; for values in force this year use get_legal_limits.

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": "get_next_year_limits"
  }
}

Input Schema

Name	Required	Description	Default
`key`	No	One item key, e.g. pension_indexation, min_wage, ike, ikze, pension_base_cap_30x, zus_full_base, ryczalt_limit. Default all.

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 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent lookup. The description adds meaningful behavioral context beyond that: the values are computed by finwire.pl from GUS/NBP data before the official act, each item carries an uncertainty interval and stage, and estimates should be presented as estimates.

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 description is front-loaded with what the tool returns and then qualifies the scope. The long item list is dense but useful because it tells the agent what categories are available; the stage taxonomy and caveat are also substantive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a read-only lookup with an output schema. The description covers scope, source, estimate status, return-item fields, stage meanings, and the contrasting sibling tool, so an agent has what it needs to call it and interpret results correctly.

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%, so the optional key parameter and examples are already well documented. The description enumerates the statutory item categories, which adds some semantic context, but it does not provide key syntax or selection rules beyond what the schema already supplies. Baseline 3 is appropriate.

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 and scope: statutory values for the next year computed from Polish legal formulas before the official act. It directly distinguishes itself from get_legal_limits, which covers values already in force this year.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative for current-year in-force values: 'for values in force this year use get_legal_limits.' It also gives presentation guidance ('Present estimates as estimates') and frames the tool as pre-official next-year estimates.

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.