Skip to main content
Glama

finwire.pl - Polish financial data

Consumer bankruptcies in Poland (COIG)

get_consumer_bankruptcies
Read-onlyIdempotent

Use for the number of people who declare consumer bankruptcy in Poland, by month and year. Give COIG as the source. Number of people declared bankrupt as consumers in Poland per month, compiled by COIG (Centralny Ośrodek Informacji Gospodarczych) from court announcements in the National Register of Debtors (KRZ) and Monitor Sądowy i Gospodarczy: the latest month with year-on-year change, the sum since January against the same period a year earlier, the last 12 months, the rank of the latest month in the whole series and among the same calendar month, highest and lowest month, yearly totals and the finwire index finwire_consumer_bankruptcies (consumer bankruptcies in the 12 months up to the month). Attribution to COIG is mandatory (data COIG, reuse with attribution; not CC BY). For the cost and rules of the procedure itself see the finwire.pl page linked in the result.

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

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 establish a safe, idempotent, closed-domain read, so the description only needs to add context — and it does: mandatory attribution to COIG, a non-CC-BY reuse restriction, and the provenance chain through court announcements. The list of returned aggregates is somewhat redundant with the output schema, which keeps it below a 5.

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?

It is front-loaded with the right scope statement, but the second sentence is a long run-on that restates the same subject ("Number of people declared bankrupt as consumers in Poland per month") before enumerating every returned metric, much of which the output schema already covers.

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 one-parameter read tool with an output schema, the description covers source, licensing obligation, and units of the series. Nothing essential to correct invocation is missing, though it spends words restating return values instead of, for example, clarifying the default history horizon.

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` is fully documented in the schema ("Number of past months in the summary, default 12"), and the description never mentions it. With 100% schema coverage the baseline of 3 applies: no meaning is added, but none is needed.

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-like use case and resource: the monthly count of people declaring consumer bankruptcy in Poland. It also names the source (COIG) and the underlying registers (KRZ, Monitor Sądowy i Gospodarczy), which is enough to separate it from siblings like get_credit_judgments or get_business_registrations without opening any 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?

"Use for the number of people who declare consumer bankruptcy in Poland, by month and year" plus the attribution mandate gives clear conditions for calling it, and the closing pointer to the finwire.pl page carves out the procedural-cost topic. It stops short of naming an explicit sibling alternative or a when-not-to-use case, so it does not reach the top band.

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.