Skip to main content
Glama

finwire.pl - Polish financial data

Forecast of the average new deposit rate in Poland (Finwire Depocast)

get_deposit_forecast
Read-onlyIdempotent

Use when the user asks if deposit rates will fall or rise, or what deposits will pay in the next months. Tell the user that it is a model estimate. For NBP rate decisions, use get_nowcast. Finwire Depocast (finwire_deposit_rate_forecast): model forecast of the average rate on new household term deposits in Polish banks (NBP MIR) 1, 3 and 6 months after the latest NBP month, with an 80% interval, the assumed NBP reference rate and backtest accuracy (error, no-change error, interval coverage). Only horizons that passed the accuracy gate are returned; hiddenHorizons counts the others. Settled earlier forecasts are compared with NBP readings. It is a model estimate, 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_deposit_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
historyNoNumber of past months of the NBP average in the summary, default 6.

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

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description still adds substantial behavior beyond them: only accuracy-gated horizons are returned, hiddenHorizons counts suppressed ones, settled forecasts are reconciled with actual NBP readings, and the payload includes the assumed reference rate plus error and interval-coverage metrics. The 'model estimate, not investment advice' caveat is a behavioral constraint the agent must relay.

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 correctly, with the trigger condition first and the tool/identifier and payload details after. Slightly over-dense in the middle (model identifier, horizon list, interval, reference rate, three accuracy metrics in one sentence) and the estimate caveat appears twice, once as an instruction and once as a closing note.

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?

Complete for a single-optional-parameter, read-only forecast tool: trigger, alternative, output composition, suppression behavior, and accuracy qualification are all covered, and an output schema exists so return shapes need no further explanation. An agent has everything needed to decide, call, and frame the result.

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?

The single parameter (history, 0-60 months, default 6) is fully documented in the schema at 100% coverage, so the baseline applies. The description never mentions this parameter or how many months of history the summary shows; it only loosely gestures at the summary block. Nothing is added beyond the schema.

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?

Names a specific resource (model forecast of the average new household term deposit rate in Poland, NBP MIR) with concrete scope (1, 3, 6 months ahead, 80% interval, backtest accuracy). It explicitly positions itself against the sibling get_nowcast, so an agent can pick between them without opening either 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 trigger ('user asks if deposit rates will fall or rise, or what deposits will pay in the next months') and an explicit routing rule for the adjacent question type ('For NBP rate decisions, use get_nowcast'). It also instructs the agent to disclose the estimate's nature to the user, which is a usage-level requirement rather than a description of output.

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.