Czech insolvency register (ISIR) — active/historical insolvency & bankruptcy by IČO or person.
Check whether a Czech company (by IČO) has any active insolvency proceeding in ISIR. Returns spisová značka, start date, and current phase if found. Returns "no record" if not (which is also informative).
| Name | Required | Description | Default |
|---|---|---|---|
| ico | Yes | Czech IČO — 7 or 8 digits. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and openWorldHint. The description adds valuable behavioral details: it returns spisová značka, start date, and current phase if found, and explicitly states what happens when no record exists ('no record'). This goes beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the action, and every sentence earns its place. No redundant or vague wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter tool with rich annotations and no output schema, the description is complete. It covers the purpose, the input, and the return behavior, giving the agent enough to invoke and interpret results correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully documents the only parameter 'ico' with its format (7-8 digits), so schema coverage is 100%. The description does not add extra parameter details beyond what the schema already provides, meeting the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool checks for active insolvency proceedings for a Czech company by IČO, with specific verb ('check'), resource ('Czech company by IČO'), and system ('ISIR'). It also distinguishes from sibling tools by focusing on IČO (company) rather than persons.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context on when to use the tool: when you have a Czech IČO and need to know about active insolvency proceedings in ISIR. It does not explicitly mention alternatives or exclusions, but the scope is evident from the phrasing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Pull a batch of recent ISIR events (insolvency register publications) since the given event id. ISIR is an append-only feed — each call returns up to ~1000 events newer than since_id. Use last_id from response as next since_id. Useful for compliance monitoring or to back-fill an index.
| Name | Required | Description | Default |
|---|---|---|---|
| since_id | No | Last seen event id. Use 0 to start from the beginning of recorded ISIR history (~2008). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnlyHint, openWorldHint), the description reveals key behaviors: ISIR is an append-only feed, each call returns at most ~1000 events, and the pagination contract via `since_id`/`last_id`. This significantly aids the agent in understanding expected results and proper invocation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the primary action and immediately followed by essential operational details. Every sentence earns its place, with no fluff or repetition of schema/annotation info.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only tool with one parameter and no output schema, the description covers purpose, usage pattern, feed characteristics, and relevant use cases. It adequately compensates for missing response schema by explaining the `last_id` cursor, making the tool self-contained for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes `since_id` with default and minimum, achieving 100% coverage. The description adds valuable context about how to use the parameter in a looping pagination pattern, which goes beyond the schema's basic field description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description begins with a specific verb ('Pull') and resource ('batch of recent ISIR events'), clearly stating what the tool does. It also distinguishes itself from siblings by focusing on the event feed polling pattern, unlike checking or searching specific records.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit usage guidance: 'Use `last_id` from response as next `since_id`' and mentions use cases (compliance monitoring, back-filling an index). However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of full differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search ISIR for an individual person (FO) by name and optional date of birth. Returns active insolvency proceedings (oddlužení / osobní bankrot). Used to screen statutory persons in KYC and DD workflows.
| Name | Required | Description | Default |
|---|---|---|---|
| dob | No | Date of birth, YYYY-MM-DD. Optional but strongly recommended — common names produce many false positives without DOB. | |
| name | Yes | Full name in any case (Czech diacritics tolerated). E.g. "Pavel Novák" or "Jana Svobodová". | |
| only_active | No | When true (default), return only currently active proceedings. False also returns closed/dismissed. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and openWorldHint annotations already establish a safe read operation. The description adds that it returns 'active insolvency proceedings' and provides Czech terminology, but does not disclose that only_active=false can return closed/dismissed cases, nor any rate limits or response format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences pack purpose, output, and use case without filler. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the rich schema and annotations, the description provides enough to select the tool. It lacks output structure details, but no output schema exists and the simple return type ('active insolvency proceedings') is sufficient for a search operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with thorough parameter descriptions (e.g., DOB's warning about false positives). The description merely restates 'by name and optional date of birth,' adding no new semantic detail beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches ISIR for an individual person by name and optional DOB, returning active insolvency proceedings. The phrase '(FO)' and 'individual person' distinguishes it from corporate lookup siblings like check_ico_insolvency.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description notes it is 'Used to screen statutory persons in KYC and DD workflows,' providing clear use context. It does not explicitly name alternative tools, but the sibling names plus the person-specific framing imply when to use this versus the ICO-based check.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
check_icocheck_ico_insolvencyget_listinglist_recent_updatespoll_isir_eventssearch_entitysearch_personsearch_person_insolvencycheck_icocheck_ico_insolvencyget_listinglist_recent_updatespoll_isir_eventssearch_entitysearch_personsearch_person_insolvencycheck_ico_insolvencydetect_address_crowdingdetect_nominee_directordetect_phoenixget_dd_reportget_risk_scoreget_risk_timelineget_statutory_chainpoll_isir_eventssearch_person_insolvencycheck_vat_payerdetect_address_crowdingdetect_nominee_directordetect_phoenixget_bank_accountsget_dd_reportget_historyget_risk_scoreget_risk_timelineget_statutariesget_statutory_chainlookup_by_icosearch_by_addresssearch_by_nacesearch_companiesvalidate_diccheck_ico_insolvencycheck_vat_payerget_bank_accountsget_historyget_statutarieslookup_by_icopoll_isir_eventssearch_by_addresssearch_by_nacesearch_companiessearch_person_insolvencyvalidate_diccheck_ico_insolvencycheck_vat_payerget_bank_accountsget_historyget_statutarieslookup_by_icopoll_isir_eventssearch_by_addresssearch_by_nacesearch_companiessearch_person_insolvencyvalidate_diccheck_ico_insolvencycheck_vat_payerget_bank_accountsget_historyget_statutarieslookup_by_icopoll_isir_eventssearch_by_addresssearch_by_nacesearch_companiessearch_person_insolvencyvalidate_diccheck_bulk_dph_payercheck_dph_payercheck_ico_insolvencylist_unreliable_payerspoll_isir_eventssearch_person_insolvencycheck_bulk_dph_payercheck_dph_payercheck_ico_insolvencylist_unreliable_payerspoll_isir_eventssearch_person_insolvencycheck_ico_insolvencypoll_isir_eventssearch_person_insolvencyClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Czech & Slovak business registry — company lookup by IČO, name, legal form, VAT. Official ARES.
Czech VAT-payer reliability (ADIS / nespolehlivý plátce DPH) + registered bank accounts by DIČ.
Czech & EU due diligence in one call — facts, insolvency, sanctions, VAT, risk score, UBO chain.
Czech distress real estate — paid tier (full search, owner data, RUIAN).
Add one secure layer between your agents and this server.
Each tool targets a distinct operation: checking a company by IČO, polling recent events, and searching by person. No functional overlap.
All tool names follow a clear verb_noun pattern (check_ico_insolvency, poll_isir_events, search_person_insolvency), ensuring predictability.
Three tools precisely cover the key interactions with the ISIR register without unnecessary bloat or missing essentials.
The set covers the three core use cases for this read-only register: company lookup, person search, and event monitoring. No obvious gaps for its domain.