Skip to main content
Glama

finwire.pl - Polish financial data

Poland against Europe

get_europe_data
Read-onlyIdempotent

Use to compare Poland with the EU: house prices, mortgage rates, bond yields, household electricity and gas prices, and minimum wages. Poland compared with EU countries: "house-prices" (Eurostat house price index), "mortgage-rates" (ECB rates on new housing loans), "bond-yields" (10-year yields and spreads vs Germany and euro area), "overburden" and "overcrowding" (housing conditions), "energy-prices" (household electricity or gas prices per kWh in EUR and purchasing power standards, half-yearly, with finwire_eu_power_price_gap and kWh per minimum wage), "minimum-wages" (statutory minimum wages in EUR and PPS, half-yearly).

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

Input Schema

NameRequiredDescriptionDefault
topicYeshouse-prices: Eurostat index. mortgage-rates: ECB rates on new housing loans. bond-yields: 10-year yields and spreads. overburden and overcrowding: housing conditions. energy-prices: household electricity or gas. minimum-wages: statutory minimum wages.
compareNoFor energy-prices and minimum-wages: EU country code (Eurostat, Greece = EL) to compare with Poland, default DE.
productNoFor energy-prices, default electricity.

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: +"house-prices: Eurostat index. mortgage-rates: ECB rates on new housing loans. bond-yields: 10-year yields and spreads. overburden and overcrowding: housing conditions. energy-prices: household electricity or gas. minimum-wages: statutory minimum wages."
  2. Changed1 schema field changed
    • addedInput schema / properties / topic / description
      Added value: +"Dataset, see the tool description."
  3. Changed3 schema fields changed
    • addedInput schema / properties / compare
      Added value: +{
      +  "description": "For energy-prices and minimum-wages: EU country code (Eurostat, Greece = EL) to compare with Poland, default DE.",
      +  "pattern": "^[A-Za-z]{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / product
      Added value: +{
      +  "description": "For energy-prices, default electricity.",
      +  "enum": [
      +    "electricity",
      +    "gas"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "house-prices",
      -  "mortgage-rates",
      -  "bond-yields",
      -  "overburden",
      -  "overcrowding"
      -]New value: +[
      +  "house-prices",
      +  "mortgage-rates",
      +  "bond-yields",
      +  "overburden",
      +  "overcrowding",
      +  "energy-prices",
      +  "minimum-wages"
      +]
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: underlying sources (Eurostat house price index, ECB rates on new housing loans), cadence (half-yearly for energy and minimum wages), and derived outputs (finwire_eu_power_price_gap, kWh per minimum wage, spreads vs Germany and euro area).

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?

The usage directive is front-loaded and the second sentence is a single organized enumeration of topics with their sources. It is dense but readable; the mild cost is that the topic list duplicates the enum descriptions already present in the schema.

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 multi-topic comparative data reader, nothing essential is missing: every topic is named with its source and cadence, annotations carry the safety profile, the input schema is fully documented, and an output schema exists so return shape need not be described. An agent can select the correct topic and call it without further information.

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 baseline is 3. The description largely restates the topic enum text and adds only marginal detail, notably that energy-prices and minimum-wages are half-yearly and that bond-yields include spreads vs Germany and the euro area. The compare and product parameters are not discussed at all, though the schema documents them fully.

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 opens with a specific verb and scope ("compare Poland with the EU") and enumerates exactly which datasets are covered (house prices, mortgage rates, bond yields, overburden/overcrowding, energy prices, minimum wages). That makes the tool's remit unmistakable. It stops short of a 5 because it never contrasts itself with the plainly related siblings (get_housing_prices, get_energy_prices), leaving the comparative vs. single-country distinction implicit.

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?

"Use to compare Poland with the EU" gives an explicit usage condition, and the per-topic breakdown tells the agent which topic value fits which question. There is no when-not guidance and no mention of when a plain single-indicator tool would be preferable, so it lands at clear-context-without-exclusions.

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.