Skip to main content
Glama

finwire.pl - Polish financial data

Regional data: income, unemployment, wages

get_regional_data
Read-onlyIdempotent

Use for data about municipalities and provinces: income, PIT, local tax, unemployment and wages. For the budget of one municipality, use get_municipal_budget. Regional data: "income" (residents income per capita by municipality, or county with level "powiat"), "pit" (PIT due per resident from tax returns by municipality and province, by type of return, PIT-38 capital gains returns per 1000 residents, finwire_pit_per_capita; with name = one municipality year by year), "local-tax" (finwire_local_tax_squeeze: property tax as % of property tax + PIT share in municipal budget plans, provinces, cities, municipalities in the squeeze, upper limit of the property tax rate for flats; with name = matching municipalities), "unemployment" (registered unemployment by province), "wages" (average wage by province). Filter by name.

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": {
      "topic": "<topic>"
    },
    "name": "get_regional_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName filter, e.g. "Gdańsk" or "pomorskie".
yearNoFor pit: tax year; for local-tax: budget year; default latest.
levelNoFor income, default gmina.
limitNoRows per list, default 10.
topicYesincome: residents income per capita. pit: PIT due per resident. local-tax: property tax share in municipal budgets. unemployment: registered unemployment by province. wages: average wage by province.

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. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"Dataset, see the tool description."New value: +"income: residents income per capita. pit: PIT due per resident. local-tax: property tax share in municipal budgets. unemployment: registered unemployment by province. wages: average wage by province."
  2. Changed1 schema field changed
    • addedInput schema / properties / topic / description
      Added value: +"Dataset, see the tool description."
  3. Changed2 schema fields changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "income",
      -  "pit",
      -  "unemployment",
      -  "wages"
      -]New value: +[
      +  "income",
      +  "pit",
      +  "local-tax",
      +  "unemployment",
      +  "wages"
      +]
    • changedInput schema / properties / year / description
      Previous value: -"For pit: tax year, default latest."New value: +"For pit: tax year; for local-tax: budget year; default latest."
  4. Changed2 schema fields changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "income",
      -  "unemployment",
      -  "wages"
      -]New value: +[
      +  "income",
      +  "pit",
      +  "unemployment",
      +  "wages"
      +]
    • addedInput schema / properties / year
      Added value: +{
      +  "description": "For pit: tax year, default latest.",
      +  "maximum": 2100,
      +  "minimum": 2000,
      +  "type": "integer"
      +}
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds a behavioural nuance — that supplying name changes the result shape (one municipality year by year; matching municipalities for local-tax) — but says nothing about pagination limits, rate limits, or what happens with invalid topic/level combinations.

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?

The purpose is front-loaded, which is good, but the body is a single run-on paragraph with long nested parentheticals that are hard to parse in one pass. It also leaks internal field names (finwire_pit_per_capita, finwire_local_tax_squeeze) that add bulk without helping an agent decide or call.

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 an output schema present and 100% parameter description coverage, the description does not need to explain return values, and it covers routing, defaults, and per-topic parameter meaning adequately. Remaining gaps are minor: no handling notes for invalid topic/level pairings and no statement of truncation behaviour beyond the limit default.

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 documents every parameter, including the per-topic meanings of topic and year. The description largely restates those glosses, with only modest added meaning (the name-filter result-shape behaviour). Baseline 3 applies when the schema carries the load.

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 opening sentence names a concrete resource domain (municipal and provincial data) and enumerates the five topics it covers, and it explicitly separates itself from get_municipal_budget. The "verb" is soft ("Use for data about"), and the tool is really a five-topic bundle, so it is clear but not razor-sharp.

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?

It gives one explicit routing rule: for the budget of a single municipality, use get_municipal_budget instead. It also implies when each topic applies via the topic glosses. It does not state exclusions against the other siblings (wages vs. average pay tools, unemployment vs. other labour tools), so the guidance is clear but not exhaustive.

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.