Skip to main content
Glama

finwire.pl - Polish financial data

Next-year property tax limits

get_property_tax_next_year
Read-onlyIdempotent

Use for the property tax on a flat or a house next year: the highest rate a municipality can set per m², before and after the Minister of Finance announcement. Tell the user the stage; an estimate is not an official value. The municipality sets its own rate up to this limit. Upper limits of the local property tax for the next year (finwire_property_tax_cap), per m² of a flat or house and for the other 8 categories of art. 5 ust. 1 of the local taxes act, from the formula in art. 20: this year limit x GUS CPI index for the first half-year, rounded up to full grosz. Stage: szacunek (estimate from monthly CPI, with 80% interval), wskaznik_gus (final figure from the GUS notice), obwieszczenie (announced by the Minister of Finance), obowiazuje (in force). Optional m2 gives the yearly maximum tax for a flat of that size. Municipalities set their own rates up to these limits; for this year limits use get_legal_limits with topic local-tax.

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

Input Schema

NameRequiredDescriptionDefault
m2NoUsable floor area of a flat or house in m² for the yearly maximum tax.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real behavioral context: the four stage values (szacunek, wskaznik_gus, obwieszczenie, obowiazuje), the warning that an estimate is not an official value, and the instruction to tell the user the stage. It does not discuss caching or data freshness beyond the stage labels, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and the stage caveat, but the sentence about municipalities setting their own rates appears twice in near-identical form, and the internal identifier (finwire_property_tax_cap) plus the art. 20 formula add density that is only partly useful to an agent.

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 need not be explained, and the description still covers the calculation basis, the category scope, the stage semantics, and the m2 option. Complete enough for correct invocation, with only the duplicated municipality sentence as noise.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single optional m2 parameter is already documented, so baseline is 3. The description adds meaning beyond the schema by explaining that m2 yields the yearly maximum tax for a flat of that size, clarifying the output effect rather than just the input type.

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 verb and resource: the maximum per-m² property tax rate a municipality may set for next year, for flats/houses plus 8 other art. 5 categories. It also names the sibling it is not (get_legal_limits for this year), so an agent can distinguish it without opening schemas.

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 says when to use it ('property tax on a flat or a house next year') and routes the this-year case to get_legal_limits with topic local-tax. The only minor gap is that it does not mention get_next_year_limits, but guidance within the definition is otherwise complete.

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.