Skip to main content
Glama

EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)

KYB check: VAT, register and sanctions

kyb_check
Read-onlyIdempotent

One-call KYB check of a supplier/customer: EU VAT validation (VIES) + official business register

  • EU/UN/OFAC/UK sanctions screening, returning a pass / review / fail verdict with reasons. company: a VAT ID ('FR40303265045'), a company name, or a registry id; country: optional ISO code (e.g. 'NO').

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": {
      "company": "<company>"
    },
    "name": "kyb_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany VAT number (best) or company name.
countryNoOptional ISO two-letter country code when a name is given.
requesterNoOptional: your own EU VAT number, so VIES returns a consultation number as audit proof.HU33119856

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / company / description
      Added value: +"Company VAT number (best) or company name."
    • addedInput schema / properties / country / description
      Added value: +"Optional ISO two-letter country code when a name is given."
    • addedInput schema / properties / requester / description
      Added value: +"Optional: your own EU VAT number, so VIES returns a consultation number as audit proof."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so safety is covered; the description adds real value by naming the external data sources consulted and the verdict taxonomy returned. It also hints that supplying a requester VAT yields an audit-proof consultation number, though it does not mention latency or rate limits inherent to hitting external registries.

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 core capability and verdict output are front-loaded in the first sentence, with parameter hints trailing. The second sentence is a slightly awkward run-on mixing 'company' and 'country' explanations, but there is no filler.

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?

With no output schema, the description correctly explains the return value (pass/review/fail with reasons). For a three-parameter read-only aggregation tool this is nearly complete; only latency, rate limits, or failure behavior when VIES/registries are unavailable are missing.

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%, so the baseline is 3. The description adds an example VAT ID format and mentions 'registry id' as an accepted input, which the schema does not, but it is silent on the requester parameter's audit-proof purpose, which only the schema documents.

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 ('KYB check'), the resource (supplier/customer), and enumerates exactly what is checked (VIES VAT, business register, EU/UN/OFAC/UK sanctions) plus the output shape (pass/review/fail with reasons). This clearly differentiates it from the narrower siblings verify_vat and screen_sanctions by describing itself as a combined one-call check.

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

Usage Guidelines3/5

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

The phrase 'One-call KYB check' implies this is the aggregate path for full onboarding due diligence, giving implied usage context. However, it never states when to prefer it over verify_vat, screen_sanctions, or check_fr_pa_registry, nor any prerequisites or cost/latency tradeoffs.

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.