Skip to main content
Glama

finwire.pl - Polish financial data

Net earnings in EU countries (Eurostat)

get_eu_earnings
Read-onlyIdempotent

Use for salaries and net pay in EU countries, how Polish pay compares with the EU or one country, and how a given net salary in PLN compares with the average in each EU country. For minimum wages, use get_europe_data. Annual net earnings (take-home pay after income tax and employee social contributions, plus family allowances) in the 27 EU countries from Eurostat earn_nt_net, yearly, by household type: single person, couples with and without children, single parent, low (67%) and high (167%) wage. Ranking in EUR and in purchasing power standards (PPS, adjusted for price levels), gross pay, tax and contributions, hourly labour cost of employers (lc_lci_lev), tax wedge of a low-wage single earner, the finwire index finwire_eu_net_wage_gap (Poland as % of the EU average in PPS) and the history of Poland and one comparison country. With salary (monthly net in PLN) it compares that pay with the average of the same household type in every EU country, in EUR and PPS, and gives the monthly EUR amount with the same purchasing power.

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

Input Schema

NameRequiredDescriptionDefault
salaryNoMonthly net salary in PLN to compare with every EU country.
compareNoEU country code (Eurostat, Greece = EL) for the history next to Poland, default DE.
householdNoHousehold type, default single (single person without children, average wage).

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 establish read-only, idempotent, non-destructive, closed-world behavior, but the description adds substantial context beyond them: data source (earn_nt_net, lc_lci_lev), yearly frequency, units (EUR and PPS adjusted for price levels), the included series (rankings, gross pay, tax and contributions, hourly labour cost, tax wedge, finwire_eu_net_wage_gap) and the extra computation triggered by `salary`. It does not discuss coverage gaps or data vintage, which keeps 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?

The usage and exclusion are correctly front-loaded, but the body is two very long run-on sentences that pack a dozen data series into comma-and-parenthesis chains, making it hard to scan. The content largely earns its place, yet the density impedes readability rather than serving concision.

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?

Return values need not be explained because an output schema exists, and the description still covers source dataset, units, breakdowns, and the effect of each optional parameter. What remains unstated (default compare country beyond the schema's 'default DE', ranking order, data recency) is minor and largely recoverable from the schema.

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 schema already documents all three parameters, but the description adds real meaning: `household` values are explained in plain terms (single person, couples with and without children, single parent, low 67% and high 167% wage) and `compare` is framed as the history shown next to Poland. `salary` is explained as producing a comparison against the same household type in every EU country in both EUR and PPS, including the equivalent monthly EUR amount at equal purchasing power.

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: annual net earnings (take-home pay after tax and social contributions plus family allowances) in the 27 EU countries from the Eurostat earn_nt_net dataset, plus the comparison behavior when a salary is supplied. It also explicitly names what it is not ('For minimum wages, use get_europe_data'), so an agent can separate it from the sibling without opening either 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 when-to-use clause ('Use for salaries and net pay in EU countries, how Polish pay compares with the EU or one country...') and adds an exclusion that routes to a named alternative for minimum wages. The conditional behavior is spelled out: supply `salary` to get a cross-country comparison, otherwise get rankings and history.

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.