Skip to main content
Glama

finwire.pl - Polish financial data

Home ownership, mortgages, financial cushion and household income in the EU (Eurostat EU-SILC)

get_eu_living_conditions
Read-onlyIdempotent

Use for how many people own their home with or without a mortgage or rent in EU countries, for people who cannot pay an unexpected expense (financial cushion) and for household income per person in EU countries. For house prices in the EU, use get_europe_data. For net pay, use get_eu_earnings. Yearly EU-SILC survey for the 27 EU countries, the EU and the euro area (Eurostat): share of people living in their own home without a mortgage, with a mortgage or housing loan, in market rent and in reduced rent or free (ilc_lvho02); share of people in households that cannot face an unexpected required expense from their own resources (ilc_mdes04); median and mean equivalised disposable income per year in EUR, PPS and PLN for Poland (ilc_di03, household income divided by the modified OECD scale; the survey year reports income of the previous year). Ranks, Poland against the EU and one comparison country with history since 2005, and two finwire indices: finwire_eu_mortgaged_owners (owners with a mortgage as % of all owners) and finwire_eu_household_income_gap (median income in Poland as % of the EU value in PPS).

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

Input Schema

NameRequiredDescriptionDefault
topicNoRanking in the summary: housing (own home and mortgage), cushion (unexpected expense) or income; default all (Poland and the EU only).
compareNoEU country code (Eurostat, Greece = EL) for the history and the comparison with Poland, default DE.

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.6/5.0
Behavior4/5

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

Annotations already establish this is a read-only, idempotent, closed-world dataset lookup, and the description adds real context beyond that: the Eurostat dataset codes (ilc_lvho02, ilc_mdes04, ilc_di03), the yearly EU-SILC source and 27-country/EU/euro-area coverage, the modified OECD equivalisation, the PLN/PPS/EUR units, and the important caveat that the survey year reports income of the previous year. It stops short of describing the ranking/history output shape, but the output schema covers that.

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?

Purpose and exclusions are front-loaded in the first two sentences, which is the right structure. The remaining middle section is a long dense run-on listing datasets, units and indices, and every clause carries information, though bullet-style segmentation would improve scannability.

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?

For a two-parameter read-only dataset tool with a full output schema, the description supplies everything an agent needs: source, coverage, dataset identifiers, units, the income-lag caveat, and the definitions of both derived finwire indices. No material gap remains.

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%, so the baseline is 3, but the description adds meaning the schema does not: it explains that the comparison country drives both the history and the Poland comparison, that the history extends back to 2005, and that the topic selection controls which ranking appears in the summary. That is a genuine increment over the enum and pattern definitions.

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 specific verbs and resources: home ownership with/without mortgage or rent, inability to pay an unexpected expense, and household income per person in EU countries. It explicitly names what it does not cover and routes those to get_europe_data and get_eu_earnings, so an agent can distinguish it from siblings without opening a schema.

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?

Opens with an explicit 'Use for...' scope statement and then gives two exclusion rules with the correct alternative for each ('For house prices... use get_europe_data', 'For net pay, use get_eu_earnings'). Nothing about when to select this tool is left to inference.

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.