finwire.pl - Polish financial data

Household fixed cost burden by province

get_fixed_cost_burden

Read-onlyIdempotent

Sztywne koszty gospodarstwa finwire (finwire_fixed_cost_burden): share of net income of a model household (two earners on the regional median wage) taken by the mortgage payment on a 50 m2 flat in the province capital, administrative fee, heating, water, waste, electricity and TV licence; Poland and 16 provinces, monthly, with the share without the mortgage.

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

Input Schema

Name	Required	Description	Default
`region`	No	'polska' or province slug, e.g. mazowieckie, slaskie, kujawsko_pomorskie; omit for all regions.
`history`	No	Number of past months in the summary for the region (Poland when omitted), default 12.

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

A3.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behaviour, so the bar is lower. The description still adds real context beyond them: the model-household methodology, the specific cost basket, the 50 m2 / province-capital assumption, monthly granularity, and the existence of a mortgage-free variant of the share.

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?

A single dense sentence that front-loads the definition and packs the methodology without filler. Minor deduction for leading with the Polish term 'Sztywne koszty gospodarstwa' before the English-language explanation, which delays the useful content slightly.

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 schema handles both parameters with defaults. The description supplies the methodological framing an agent needs to interpret the numbers; the only real gap is the absence of routing guidance among the many housing and regional siblings.

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%, so the schema already explains both region and history fully; baseline 3 applies. The description contributes only indirectly by stating that the data spans Poland and 16 provinces (hinting at valid region values) and is monthly (relevant to history), without adding syntax or defaults.

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 precisely defines the metric: fixed-cost share of net income for a model two-earner household, itemised (mortgage on a 50 m2 flat, admin fee, heating, water, waste, electricity, TV licence), with coverage stated as Poland plus 16 provinces and monthly frequency. It is specific enough to distinguish it from get_housing_costs, get_rents and get_housing_carry by construction, though it never names those siblings or states an explicit verb.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of adjacent tools (get_housing_costs, get_rents, get_housing_carry, get_regional_data), and no mention of how to choose between them. Usage can only be inferred from the metric definition itself.

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.