Skip to main content
Glama

VeriActa: company registers

company_lookup
Read-onlyIdempotent

A company in a country's public registers on a given day: tax status, register entry and who may represent it, and whether a bank account is registered for it. Use it to check a counterparty before a payment or a contract, with the account to be paid in account. The registered accounts are listed only with list_accounts, and people's names in the register's text are masked. Say which register and day each fact comes from. A result that a service did not answer is not a negative result.

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": {
      "jurisdiction": "<jurisdiction>",
      "id": "<id>"
    },
    "name": "company_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe company's number: a tax number or a register number (Poland: NIP, KRS or REGON; dashes, spaces and a country prefix are fine).
dateNoThe day to check the status and bank accounts on, YYYY-MM-DD. Today when left out.
accountNoA bank account to check: the result's `account_check` says whether it is registered for the company on `date` (Poland: the VAT white list; spaces and PL are fine). Pass the account to be paid.
id_typeNoWhich number `id` is, when you know. Left out, the number is recognised by its form.
jurisdictionYesThe country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR, SE, IT, GB (UK = GB).
list_accountsNotrue lists every bank account registered for the company. Leave it out unless the user asks for the list: the result gives their number, and `account` checks one.

Output Schema

NameRequiredDescriptionDefault
krsNoThe court register entry: representation, board, proxies, capital (Poland). People's names in the register's text are masked.
vatNoVAT status on the date and its history, and how many bank accounts are registered (`bank_accounts_count`; the accounts themselves only with `list_accounts`).
modeNoThe identifier the company was looked up by.
foundNoWhether any register returned the company.
queryNoThe identifiers and the date asked for.
vat_euNoEU VAT number validity (VIES); `valid` is null when the service did not answer, which is not a refusal.
companyNoName, identifiers, legal form, address and status in the register.
sourcesNoThe registers the answer was read from, with their addresses.
warningsNoNotes to read before answering: what was not found, not confirmed or may be out of date.
account_checkNoFor an `account` asked about: whether it is registered for the company on the date (`registered` true or false; null when it could not be checked, with the reason in `warnings`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "A bank account to check: the result's `account_check` says whether it is registered for the company on `date` (Poland: the VAT white list; spaces and PL are fine). Pass the account to be paid.",
      +  "maxLength": 60,
      +  "type": "string"
      +}
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR, GB, SE, IT (UK = GB)."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR, SE, IT, GB (UK = GB)."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK",
      -  "NL",
      -  "IE",
      -  "FI",
      -  "FR",
      -  "GB",
      -  "SE",
      -  "IT",
      -  "UK"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL",
      +  "IE",
      +  "FI",
      +  "FR",
      +  "SE",
      +  "IT",
      +  "GB",
      +  "UK"
      +]
    • addedInput schema / properties / list_accounts
      Added value: +{
      +  "description": "true lists every bank account registered for the company. Leave it out unless the user asks for the list: the result gives their number, and `account` checks one.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / account_check
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "For an `account` asked about: whether it is registered for the company on the date (`registered` true or false; null when it could not be checked, with the reason in `warnings`)."
      +}
    • changedOutput schema / properties / krs / description
      Previous value: -"The court register entry: representation, board, proxies, capital (Poland)."New value: +"The court register entry: representation, board, proxies, capital (Poland). People's names in the register's text are masked."
    • changedOutput schema / properties / vat / description
      Previous value: -"VAT status on the date, its history and the registered bank accounts."New value: +"VAT status on the date and its history, and how many bank accounts are registered (`bank_accounts_count`; the accounts themselves only with `list_accounts`)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR, GB (UK = GB)."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR, GB, SE, IT (UK = GB)."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK",
      -  "NL",
      -  "IE",
      -  "FI",
      -  "FR",
      -  "GB",
      -  "UK"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL",
      +  "IE",
      +  "FI",
      +  "FR",
      +  "GB",
      +  "SE",
      +  "IT",
      +  "UK"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR, GB (UK = GB)."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK",
      -  "NL",
      -  "IE",
      -  "FI",
      -  "FR"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL",
      +  "IE",
      +  "FI",
      +  "FR",
      +  "GB",
      +  "UK"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK",
      -  "NL",
      -  "IE"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL",
      +  "IE",
      +  "FI",
      +  "FR"
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK",
      -  "NL"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL",
      +  "IE"
      +]
  6. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL"
      +]
  7. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK"
      +]
  8. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, and the description adds real context beyond them: people's names in register text are masked, each fact must be attributed to a register and a day, and an unanswered service is explicitly not a negative result. The provenance sentence is slightly ambiguous about whether the register/day attribution comes from the tool's output or must be supplied by the agent.

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?

Five dense sentences with no filler, each carrying a distinct fact (content, trigger, account routing, masking, provenance, partial-failure). The provenance instruction is the least clear sentence and could be sharper, but nothing is redundant.

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?

For a read-only lookup with an output schema, the description covers the important non-obvious behaviors: masked names, required attribution, and the distinction between no-answer and negative-answer. The one unaddressed case is what happens for a jurisdiction outside the live list, which is implied but never stated.

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%, so the baseline is 3, but the description adds genuine routing meaning: `account` should carry the account being paid, and `list_accounts` is the only way to enumerate registered accounts and returns their number. That clarifies the relationship between two parameters the schema documents separately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely (a company in a country's public registers on a given day) and enumerates the returned facts: tax status, register entry and representation, and bank-account registration. It is clearly distinct from siblings like law_lookup or classification_lookup, though the opening is a noun phrase rather than a verb, so the action (lookup) is only implied by the usage sentence.

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?

"Use it to check a counterparty before a payment or a contract, with the account to be paid in `account`" gives a concrete trigger and the parameter choice that follows from it. It also steers away from the `list_accounts` mode unless the user asks for the list. It does not explicitly exclude or route to any sibling tool, keeping it short of a 5.

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.