Skip to main content
Glama

finwire.pl - Polish financial data

Finwire Nowcast: inflation and RPP forecasts

get_nowcast
Read-onlyIdempotent

Use for the next CPI or core inflation value and the next RPP decision. Tell the user that this is a model estimate. Give the interval or the probabilities, and the accuracy. For past accuracy, prefer the live track record over the backtest. Write the source as "Finwire Nowcast (finwire.pl)". Finwire Nowcast (finwire id: finwire_nowcast), the finwire.pl statistical model of the next official readings: CPI inflation y/y and core inflation y/y (point and 80% interval) and probabilities of a cut, no change or hike at the next RPP (Monetary Policy Council) meeting. Recomputed daily, frozen 3 working days before publication, then settled against the actual reading; with backtest accuracy vs naive benchmarks and the live track record (each forecast published before the reading vs the first official reading). A model estimate, not a consensus and not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
historyNoRecent settled or backtest points per indicator, default 6.
indicatorNoOne indicator; omit for all three.

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

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

Annotations already declare readOnly/idempotent/closed-world, but the description adds real behavioral context: recomputed daily, frozen three working days before publication, settled against the actual reading, and both backtest-vs-naive-benchmark and live track record accuracy. It also warns that the output is a model estimate rather than a consensus, which is important framing for how the agent should relay it.

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 lead sentence is well front-loaded, but the text mixes agent output instructions (cite the source as "Finwire Nowcast (finwire.pl)", tell the user it is a model estimate) with tool semantics, and the "model estimate, not a consensus" point is stated twice. The title and identifier are restated mid-paragraph, adding bulk without new meaning.

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, return values need not be described, and the description covers the forecast lifecycle, freeze window, and accuracy provenance needed to use the numbers responsibly. The only soft gap is that it does not say what the tool returns during the frozen pre-publication window or when an indicator is unavailable.

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 (indicator enum, history count with default) are documented in the schema itself. The description only implicitly maps to the indicator parameter by listing CPI, core and RPP, and adds no format or interpretation detail beyond the schema. Baseline 3 applies.

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 names the exact outputs: next CPI y/y and core inflation y/y (point plus 80% interval) and probabilities of cut/no-change/hike at the next RPP meeting. That is a specific verb+resource statement an agent can match to a request. It does not explicitly differentiate itself from data siblings such as get_eu_inflation or get_lead_forecasts, so it stops short of a 5.

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 for the next CPI or core inflation value and the next RPP decision" gives clear triggering context, and "For past accuracy, prefer the live track record over the backtest" resolves an in-tool choice. It never states when not to use it or names an alternative data tool, so there is no explicit alternative routing.

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.