Skip to main content
Glama
ucetka-mcp

ucetka-mcp

Look up company in ARES

lookup_company
Read-onlyIdempotent

Verify a Czech company by IČO against the official ARES registry to retrieve its name, address, DIČ and VAT payer status before invoicing. Read-only lookup for customer checks.

Instructions

Look up a Czech company in the public ARES registry (Ministry of Finance) by IČO (company ID) and return its official name, registered address, DIČ (VAT ID) and whether it is an active VAT payer.

Read-only: makes one HTTPS request to ares.gov.cz and saves nothing. Use it to verify a customer before invoicing; to also store the company in the address book use add_customer instead (it does the same lookup). Fails with CompanyNotFound if the IČO does not exist, or with an HTTP/network error if ARES is unreachable.

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": "lookup_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
icoYesCzech IČO (company ID): exactly 8 digits incl. leading zeros, e.g. '27082440'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ico / description
      Previous value: -"IČO firmy (8 číslic)."New value: +"Czech IČO (company ID): exactly 8 digits incl. leading zeros, e.g. '27082440'."
    • addedInput schema / properties / ico / pattern
      Added value: +"^\\d{8}$"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, but the description still adds real behavior: exactly one HTTPS request to ares.gov.cz, nothing persisted, and named failure modes (CompanyNotFound for a bad IČO, HTTP/network error when ARES is unreachable). The enumeration of returned fields is partly redundant with the output schema, which keeps it from 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.

Conciseness4/5

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

Front-loaded with purpose, then behavior, then error modes, in three short paragraphs with no filler. The only slack is the return-field list that the output schema already supplies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with rich annotations and an output schema, the description covers everything an agent needs: what it does, network/state side effects, and the failure surface. Nothing further is required to call it correctly.

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% and the schema already specifies the 8-digit pattern and an example, so the baseline would be 3. The description adds modest meaning by framing ico as the Czech company ID used to key the registry lookup, slightly above baseline but not materially beyond the schema.

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?

States a specific verb (look up), resource (Czech company), source registry (public ARES, Ministry of Finance), key identifier (IČO), and what comes back (official name, address, DIČ, VAT-payer status). It also names the sibling add_customer and how it differs, so an agent can discriminate without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case (verify a customer before invoicing) and an explicit alternative with its selection condition: use add_customer when the company should also be stored in the address book, since it performs the same lookup. Both when-to-use and when-to-use-something-else are present.

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