Skip to main content
Glama

finwire.pl - Polish financial data

Retail savings bond sales in Poland (Ministry of Finance)

get_savings_bond_sales
Read-onlyIdempotent

Use for how many savings bonds people buy in Poland, which series sell best, the sum since January against earlier years, IKE and IKZE purchases and buyer age. For bonds against deposits, use get_retail_bond_premium. For the rate in the next interest period, use get_bond_next_rate. Retail savings bonds of the State Treasury sold in Poland per month, from the Ministry of Finance statistics on gov.pl (since January 2015): the latest month in PLN with month-on-month and year-on-year change, the share and amount of every series (OTS, ROR, DOR, TOS, COI, EDO, family ROS and ROD), money from the exchange of maturing bonds and new money, purchases on IKE and IKZE retirement accounts, sales channels, buyer age (natural persons), the sum since January with the rank against the same months of every year, the best month and year, and the finwire index finwire_savings_bond_sales (sales in the 12 months, PLN billion). For interest rates of the current issue use get_retail_bond_premium or get_bank_rates.

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

Input Schema

NameRequiredDescriptionDefault
historyNoNumber of past months in the summary, default 12.

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

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds genuinely useful scope context beyond annotations: coverage starts January 2015, figures are monthly PLN with MoM and YoY change, and the finwire_savings_bond_sales index reflects a trailing 12-month window in PLN billions. It stops short of noting refresh cadence or lag for the latest month, which would matter for a statistics tool.

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 front-loaded use-case sentence and sibling routing are well placed, but the second sentence is a very long run-on enumeration of every returned field, much of which duplicates the output schema. It is informative yet bloated and harder to scan than a short purpose statement plus a bulleted or trimmed content summary.

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 full annotations, a documented single parameter, an output schema, and detailed content coverage, the definition is sufficient to call the tool correctly. The only misses are the unexplained 'history' window and any note on data recency, both minor for a read-only statistical endpoint.

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?

There is a single parameter, 'history' (0–60, default 12), and schema description coverage is 100%, so the schema already carries the meaning. The description never mentions the window/lookback control at all, leaving it to the schema alone; baseline 3 is appropriate but no extra value is added.

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?

The description names a specific verb+resource (retail savings bond sales of the State Treasury in Poland, monthly, from Ministry of Finance / gov.pl) and enumerates the exact contents: series breakdown (OTS, ROR, DOR, TOS, COI, EDO, ROS, ROD), new vs. exchanged money, IKE/IKZE purchases, sales channels, and buyer age. It is immediately distinguishable from the rate-oriented siblings, so an agent can tell what this returns 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 Guidelines4/5

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

It gives explicit routing: 'For bonds against deposits, use get_retail_bond_premium' and 'For the rate in the next interest period, use get_bond_next_rate.' The closing sentence, however, reassigns get_retail_bond_premium to 'interest rates of the current issue' alongside get_bank_rates, which mildly conflicts with the earlier deposit-comparison assignment and leaves the premium tool's role ambiguous.

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.