Skip to main content
Glama

finwire.pl - Polish financial data

Poland compared with the world (BIS, OECD): central bank rates, house prices, credit cycle, Finwire Housecast

get_world_comparison
Read-onlyIdempotent

Use for Poland against other countries: central bank rates and the NBP rate rank, real house prices abroad, price to income or rent, credit gap, and whether Polish housing is overvalued (Finwire Housecast). Say that a forecast is a model estimate. Poland against other countries from the BIS (Bank for International Settlements) and the OECD. topic policy_rates: central bank policy rates of BIS economies, the place of the NBP rate (finwire_policy_rate_rank, 1 = highest rate) nominal and real (rate minus annual CPI inflation), median, rank history, real effective exchange rate of the zloty. topic house_prices: real and nominal annual change of residential property prices by country with the place of Poland, and price-to-income and price-to-rent ratios of Poland and the OECD average. topic credit_cycle: credit-to-GDP gap of Poland and the debt service ratio of the private non-financial sector (no household-only ratio for Poland). topic housecast: Finwire Housecast (finwire_housing_valuation_gap), the housing valuation gap of Poland and panel countries and the model forecast of real house prices 4 and 8 quarters ahead; a horizon below the accuracy gate has no numbers.

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhat to compare, default policy_rates.
countryNoCountry code (ISO 3166 alpha-2, euro area = XM) to show next to Poland in policy_rates and house_prices.

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

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses the upstream sources (BIS, OECD), the meaning of finwire_policy_rate_rank (1 = highest rate), a data limitation (no household-only debt service ratio for Poland), and an accuracy gate that suppresses forecast numbers below a horizon. It also imposes a presentation obligation ('Say that a forecast is a model estimate'), which is genuinely useful behavioral context not captured anywhere in the structured fields.

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 'topic X:' segmentation gives useful structure and the use case is front-loaded, but the text is long and repetitive — 'Poland against other countries' appears twice and 'Finwire Housecast' is restated across several sentences. It is comprehensible but not tight.

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, the description does not need to explain return shapes, and it correctly concentrates on topic coverage, data sources, and caveats such as the forecast accuracy gate. The one gap is how it relates to overlapping siblings, which keeps it short of full completeness for a multi-topic aggregator.

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 goes further by explaining what each of the four topic enum values actually returns, including the specific derived metrics (rank history, real effective exchange rate, price-to-income, 4- and 8-quarter forecasts). The country parameter's role is confirmed ('next to Poland') rather than expanded, so it is an increment, not a full elaboration.

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 states a specific scope — Poland compared against other countries — and the four 'topic X:' segments enumerate the concrete content (policy rates and NBP rank, real house prices, credit-to-GDP gap, Housecast valuation gap). It is clear what the tool returns, though it never distinguishes itself from similarly-named siblings such as get_oecd_comparison or get_housing_prices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use for Poland against other countries' gives a starting context, and the per-topic breakdown implies which topic value answers which question. However, there is no when-not guidance and no pointer to an alternative tool for overlapping data (e.g. OECD comparisons or plain housing prices), so routing depends on 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.