Skip to main content
Glama

finwire.pl - Polish financial data

Forecasts for Poland: European Commission, OECD, NBP, Finwire Nowcast

get_poland_forecasts
Read-onlyIdempotent

Use for forecasts of GDP growth, inflation, unemployment, deficit and public debt of Poland for this and next year from the European Commission, OECD and NBP, how forecasts changed and which institution was most accurate. Say which institution and edition each number comes from and that these are forecasts, not finwire.pl advice. For the next CPI reading or RPP decision, use get_nowcast. Latest edition of every institution with forecasts of real GDP growth, annual average inflation (European Commission: HICP; NBP, OECD and Finwire Nowcast: CPI), unemployment (LFS), general government balance and debt as % of GDP for the current and next years, the previous edition, outturns, mean forecast errors of each institution (forecasts made a year earlier) and the finwire index finwire_forecast_accuracy. Every edition is stored separately (European Commission since spring 2011). Finwire Konsensus is included only for indicators where it beat the best single institution in the backtest. Optional year selects the target year in the summary.

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

Input Schema

NameRequiredDescriptionDefault
yearNoTarget year in the summary; default the year after the latest European Commission edition.

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
Behavior5/5

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

Annotations already declare a safe read-only, idempotent, closed-world operation, but the description adds non-obvious behavior: every edition is stored separately (European Commission since spring 2011), previous editions and outturns are included, and mean forecast errors are computed from forecasts made a year earlier. It also imposes an attribution obligation (name institution and edition, flag these as forecasts, not finwire.pl advice) that an agent would never infer from annotations alone.

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 routing sentence and the get_nowcast exclusion are correctly front-loaded, but the second half is a long, comma-chained enumeration of every indicator, edition and derived statistic that reads like a data catalog. Much of that content restates what the output schema already defines, so the definition is longer than its added value warrants.

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?

For a read-only, single-optional-parameter tool with an output schema, the description covers the source institutions, historical coverage, accuracy benchmarking and the required disclaimer, which is enough to call it correctly. The only shortfall is that return-shape detail is expanded in prose where the output schema would have sufficed.

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 the only parameter's description already explains that it sets the target year and defaults to the year after the latest European Commission edition. The description's line "Optional year selects the target year in the summary" restates the schema rather than adding format or precedence detail, so 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?

Opens with a specific verb+resource+scope: forecasts of GDP growth, inflation, unemployment, deficit and public debt for Poland, naming the three institutions (European Commission, OECD, NBP) plus the Finwire Nowcast and accuracy comparison. It is clearly separable from get_nowcast, which it names, so an agent can pick it without opening the 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?

Gives an explicit when-to-use ("Use for forecasts... for this and next year") and an explicit when-to-use-something-else ("For the next CPI reading or RPP decision, use get_nowcast"). It also states a selection rule for what is included (Finwire Konsensus only where it beat the best single institution in the backtest), removing ambiguity about scope.

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.