Skip to main content
Glama

finwire.pl - Polish financial data

Household savings in Poland: financial assets by instrument, invested share, Poland vs OECD

get_household_savings
Read-onlyIdempotent

Use for how much money households in Poland hold and where: cash, bank deposits, bonds, shares, investment funds, insurance and pension savings, the share outside cash and deposits, and Poland against OECD countries. Give NBP (via the ECB) and OECD as sources and the quarter or year. Financial assets of households in Poland at the end of each quarter since 2003 from the quarterly financial accounts compiled by NBP and published by the ECB (QSA): total, cash, deposits, debt securities, equity, investment funds, life insurance, pension entitlements and other, in PLN billion with shares and year-on-year change; finwire_household_invested_share (Udział oszczędności pracujących finwire: share of financial assets outside cash and deposits, i.e. debt securities, equity and funds, insurance and pension entitlements); Poland among countries in the OECD financial dashboard (share of currency and deposits with rank, equity, funds, pension; net financial worth per person in USD PPP); investment funds, PPK, IKE and IKZE and retail savings bond sales from other finwire datasets.

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

Input Schema

NameRequiredDescriptionDefault
quartersNoNumber of past quarters in the summary, default 8.

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?

Beyond the annotations, the description discloses sources (NBP via ECB, OECD), time coverage (quarterly since 2003), units (PLN billion with shares and year-on-year change), specific series names, and ranking details. This adds substantial behavioral context about what the tool returns.

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 first clause is front-loaded with the use case, but the second sentence is a massive semicolon-separated list mixing instruments, series names, OECD comparisons, and other datasets. It is dense and could be structured more clearly, though most content is relevant.

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?

Given the tool's complexity, output schema, and annotations, the description is largely complete. The only ambiguity is whether retail savings bond sales are included in this tool's output or merely referenced from other datasets, and the overlap with get_oecd_comparison is not resolved.

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% and the single parameter (quarters) is fully documented in the schema. The description does not mention the parameter at all, so it adds no meaning beyond what the schema already provides; 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 states a specific verb and resource: household financial assets in Poland by instrument, invested share, and Poland vs OECD. It does not clearly differentiate this from the sibling get_oecd_comparison, which likely also covers OECD comparisons, and it mentions 'other finwire datasets' without making the boundary explicit.

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?

It opens with an explicit 'Use for' statement and lists the exact data types and comparisons covered. However, it gives no when-not guidance or alternative routing, and it does not say when to use this tool versus get_oecd_comparison.

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.