Skip to main content
Glama

check_czech_company_kyb

Read-onlyIdempotent

Look up one Czech business by IČO in ARES. Returns its name, registry flags, VAT reliability and published bank accounts from ADIS for registered VAT payers. UNKNOWN means evidence is incomplete. Use verify_eu_vat_vies for EU cross-border VAT registration.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ico": "<ico>"
    },
    "name": "check_czech_company_kyb"
  }
}

Input Schema

NameRequiredDescriptionDefault
icoYesCzech business identifier as text, e.g. 00094943. Preserve leading zeros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / ico / description
      Previous value: -"8-digit Czech company IČO"New value: +"Czech business identifier as text, e.g. 00094943. Preserve leading zeros."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: bank accounts come from ADIS and only exist for registered VAT payers, and an UNKNOWN result signals incomplete evidence rather than a negative finding. Unexplained are error handling for an invalid IČO and the meaning of the 'registry flags' field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with zero filler: purpose first, then return contents and the UNKNOWN semantics, then the sibling escape hatch last. Every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, so the description must carry return-value meaning, and it does name the field categories and explain the UNKNOWN sentinel — the single most important output semantic. For a one-parameter read-only lookup this is close to sufficient, though a brief note on invalid-IČO or not-found behavior would close the remaining gap.

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?

Schema coverage is 100% and the single parameter already carries its own description including the leading-zero caveat, so the schema does the heavy lifting. The description only restates that the lookup key is an IČO; it adds no format, validation or fallback semantics beyond what the schema provides, which puts it at the baseline.

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 opening sentence names a specific verb (look up), a precise resource (one Czech business), an identifier (IČO) and the backing registry (ARES), then lists the returned fields. It also explicitly distinguishes itself from the sibling verify_eu_vat_vies, so an agent can separate the two without opening either 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 an explicit routing rule to a named alternative for EU cross-border VAT registration, and the phrase 'one Czech business by IČO' implicitly scopes use to single-entity domestic lookups. It does not state exclusions such as how to handle non-Czech entities or batch lookups, so the guidance stops short of full when/when-not coverage.

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.