Skip to main content
Glama

regdata_krz_debtor

Check Poland's official KRZ debtor registry for bankruptcies and restructurings. Search by entity, person, or case; retrieve trustee estate inventories with valuations for creditor recovery.

Instructions

Poland KRZ National Debtor Registry Scraper. Automate bankruptcy and restructuring checks against the official public debtor registry. Nine search modes cover companies, persons, sole traders, case signatures, proceedings, shareholders, and assets. The bankruptcyEstate mode returns the trustee's filed estate inventory (spis masy upadlosci) for a company's proceedings - real estate, movables, cash, property rights and receivables, each with the trustee's own valuation, quantity and status. Pass entityName and/or identifier (proceedings are resolved for you) or a proceedingId; estateInventoryPublished:false means the register reports zero assets for that proceeding - a verified zero, not a failed lookup. For distressed-asset sourcing and creditor recovery-prospect assessment. Build a credit-risk watchlist or insolvency workflow. Pay-per-result. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateToNoEnd date for announcement search (YYYY-MM-DD). Only used in announcements mode.
dateFromNoStart date for announcement search (YYYY-MM-DD). Only used in announcements mode.
maxItemsNoOptional cap on billed dataset items returned.
entityNameNoCompany name, business name, or advisor surname (partial match). Used for entity, soleTrader, announcements, shareholders, bankruptcyEstate, and advisors modes.
identifierNoEntity identifier: KRS (10 digits), NIP, REGON. For persons: PESEL or NIP. For advisors: license number.
maxResultsNoMaximum number of results to return. Default: 100. Set to 0 for unlimited.
searchModeNoWhat to search for. 'entity' = companies by name/KRS/NIP. 'person' = natural persons by PESEL/NIP. 'soleTrader' = sole traders by name/identifier. 'signature' = by court case signature. 'announcements' = court announcements. 'shareholders' = partners in personal companies. 'bankruptcyEstate' = assets for sale from bankruptcy estates. 'advisors' = licensed restructuring advisors. 'proceedingDetails' = deep-dive into a specific proceeding.entity
advisorCityNoFilter restructuring advisors by city. Only used in advisors mode.
proceedingIdNoProceeding UUID (postepowanieId), as returned in the `proceedingId` field of an entity/person search. Used by searchMode 'proceedingDetails', and optionally by 'bankruptcyEstate' to read one specific estate.
caseSignatureNoCourt case signature in format: CODE/REPERTORY/NUMBER/YEAR (e.g., WA1M/GU/223/2021). Used for signature and announcements modes.
disableSessionCacheNoAdvanced. By default the actor caches the KRZ guest token between your own runs (the token lives ~10h) so repeated/monitoring runs skip the slow browser bootstrap and run faster. The cache is private to your account and self-healing (a stale token is detected and refreshed automatically). Turn this on only to force a fresh session every run for debugging.
Behavior4/5

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

Despite no annotations, the description discloses pay-per-result model, session caching behavior (in parameter description), that proceedings are resolved automatically, and the meaning of estateInventoryPublished:false. It could mention error handling or rate limits, but overall provides substantial behavioral insight.

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?

The description is a single, well-structured paragraph that front-loads the main purpose and then details key features. It is informative without excessive verbosity, though slightly dense.

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 (11 params, no output schema), the description covers essential aspects: search modes, core parameter usage, and a key mode's output. It omits full output structure for all modes, but the provided detail suffices for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds value by explaining mode semantics (e.g., bankruptcyEstate specifics) and how entityName/identifier interact. This enhances understanding beyond the schema's short descriptions.

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?

Description clearly identifies the tool as a scraper for Poland KRZ National Debtor Registry, specifying it automates bankruptcy and restructuring checks. It lists nine search modes, making the purpose distinct from sibling tools that cover other registries.

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?

Description provides use cases (distressed-asset sourcing, creditor recovery, credit-risk watchlist, insolvency workflow) and directs to regdata_describe for advanced fields. It does not explicitly contrast with siblings, but the unique registry focus makes usage context clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nolpak14/getregdata'

If you have feedback or need assistance with the MCP directory API, please join our Discord server