Skip to main content
Glama

regdata_czech_isir_insolvency

Check Czech insolvency statuses by searching the official ISIR register with company name, IČO, or city. Get case reference, court, and proceeding status for risk screening.

Instructions

Czech ISIR Insolvency Register Search. Search the Czech insolvency register (ISIR) by company or debtor name, IČO or city. Get debtor name, IČO, case reference, court, proceeding status and the commercial-register cross-link. The register serves at most 400 rows per search and REFUSES a broader query outright - a refusal is reported as such and is NOT "no records". includeEnded defaults to true, which pulls in closed proceedings and makes a common surname more likely to be refused; set it false or add the IČO/city and re-run. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icoNoOne or more Czech IČO registration numbers to look up (e.g. "41035623").
cityNoOptional city (obec) to narrow the search.
nameNoThe debtor to look up: a company name or a person's surname. Matched against the ISIR debtor index. Leave empty when using a watchlist.
maxItemsNoOptional cap on billed dataset items returned.
firstNameNoOptional first name to narrow an individual-debtor search.
watchlistNoA list of company names or surnames to check in one run - ideal on a schedule to monitor your counterparties for new Czech insolvencies. Overrides "name".
maxResultsNoMaximum debtor records to export across all queries (the register returns up to 400 per query).
includeEndedNoOn (default): include closed/ended insolvency proceedings as well as active ones. Off: only currently-active proceedings.
Behavior4/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It reveals that the register refuses broad queries outright, that refusals are reported distinctly from 'no records,' and explains the impact of includeEnded on refusal likelihood. It also notes acceptance of advanced fields and no API key requirement, though it does not detail rate limits or error handling.

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 relatively concise for the amount of information conveyed, front-loading the main purpose and then covering limitations and tips. It could be slightly more structured but remains readable and efficient.

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 no output schema, the description lists key return fields and warns about refusal behavior. It covers important usage nuances (includeEnded, watchlist, maxResults) and mentions advanced fields via regdata_describe. It does not detail the return format or error handling, but is fairly complete for a data search tool.

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 description coverage is 100%, but the description adds significant value beyond the schema by clarifying behavioral aspects: includeEnded's default effect, watchlist overriding 'name' parameter, and maxResults capping export. It also mentions additional accepted properties.

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 clearly states the tool searches the Czech ISIR Insolvency Register by company name, debtor name, IČO, or city, and lists returned fields (debtor name, IČO, case reference, court, status, cross-link). It differentiates from sibling tools (various country-specific registers) by specifying jurisdiction and function.

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?

The description provides practical guidance on query limits (400 rows), behavior of includeEnded flag (default true causing potential refusals), and suggests narrowing with IČO/city or setting includeEnded false. It does not explicitly state when not to use, but the limitations are well explained.

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