Skip to main content
Glama

finwire.pl - Polish financial data

Unemployment in EU countries (Eurostat)

get_eu_unemployment
Read-onlyIdempotent

Use to compare unemployment in Poland with EU countries, also youth unemployment. For registered unemployment in Polish voivodeships, use get_regional_data. Monthly unemployment rate in the 27 EU countries, the EU and the euro area from Eurostat (une_rt_m, seasonally adjusted, ILO definition from labour force surveys): total and persons under 25, rank from the lowest rate, change vs the previous month and a year earlier in percentage points, rank of Poland in every month since 2010, history of Poland, the EU, the euro area and one comparison country, and the finwire index finwire_eu_youth_unemployment_ratio (youth rate divided by the total rate in Poland). This is not the registered unemployment rate of Polish labour offices (GUS); for that and for voivodeships use get_regional_data with topic unemployment.

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

Input Schema

NameRequiredDescriptionDefault
compareNoEU country code (Eurostat or ISO, Greece = EL or GR) to compare with Poland, default DE.
historyNoNumber of past months in the summary, default 12.

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 cover the safety profile (readOnly, idempotent, not destructive, closed-world), so the description's job is to add context beyond that — and it does: it names the underlying dataset, the seasonal adjustment and ILO definition, and warns this is not the GUS registered rate, which prevents a serious misreading of the numbers. It also enumerates what the response contains (rankings, month-over-month and year-over-year change in pp, Poland's rank since 2010, the finwire youth ratio), though that overlaps with the existing output schema.

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?

Front-loaded with the use case and the sibling exclusion, then the technical detail. It is dense and long, and the enumeration of every returned series borders on restating the output schema, but each clause carries information and there is no filler.

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, fully-described, output-schema-backed read tool this is more than sufficient: scope (27 EU countries, EU, euro area, monthly), methodology, the alternative tool for a commonly confused metric, and the derived index are all stated.

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 coverage is 100% and both parameters (compare country code with EL/GR handling and a default of DE, history months defaulting to 12) are fully documented in the schema. The description never mentions either parameter, so it adds no meaning beyond structured data — the baseline 3 applies.

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 (compare unemployment in Poland vs EU countries, plus youth unemployment) and explicitly names the sibling it is not (get_regional_data for registered/voivodeship unemployment). The data source (Eurostat une_rt_m, seasonally adjusted, ILO definition) further pins down what this tool returns.

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?

Gives an explicit when-to-use ('Use to compare unemployment in Poland with EU countries, also youth unemployment') and an explicit when-not-to plus the alternative ('for registered unemployment of Polish labour offices (GUS) … use get_regional_data with topic unemployment'). Nothing about routing 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.