Skip to main content
Glama

kyb_check_eu

Verify an EU company's KYB status by VAT number with VIES validity, sanctions screening, LEI candidates, and national register checks, returning a pass/review/fail verdict.

Instructions

One-call KYB for any EU company by VAT number: VIES validity with registered name/address, sanctions screening (US CSL/OFAC, EU, FR, UK) of the name, GLEIF LEI candidates, plus national register data for France (Sirene + BODACC proceedings) and Finland (PRH), with a pass/review/fail verdict. Costs 0.01 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "vat": "<vat>"
    },
    "name": "kyb_check_eu"
  }
}

Input Schema

NameRequiredDescriptionDefault
vatYesEU VAT number with country prefix
nameNoCompany name if VIES does not publish it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, this description carries the full burden and does most of it: it discloses the per-call price (0.01 USDC on Base via x402) and, critically, that an unauthenticated call returns a 402 payment challenge rather than a result — exactly the behavior an agent needs to avoid a confusing failure. Still missing are failure/error semantics (e.g. what a VIES-down or invalid-format VAT yields), which matters for a multi-source aggregation call.

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?

The capability and its scope come first, the data sources follow as a compact list, and the cost/payment caveat is a short second sentence. Every clause carries information an agent needs; there is no filler or restatement of the name.

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?

No output schema exists, so the description compensates by naming the verdict vocabulary (pass/review/fail) and the constituent checks. Combined with the payment/402 disclosure and full schema coverage on two parameters, nothing essential for correct invocation is 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 both parameters are already documented, and the description adds only indirect meaning — that the name is used for sanctions screening and that VIES is the primary identity source. Baseline 3 is appropriate given the schema does the per-parameter explaining.

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 and resource ('One-call KYB for any EU company by VAT number') and then enumerates exactly which sources are queried (VIES, sanctions lists, GLEIF LEI, Sirene/BODACC, PRH) and what comes out (pass/review/fail). The 'any EU company' scoping distinguishes it from the country-specific siblings kyb_check_fr and kyb_check_uk.

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?

The description makes clear this is the broad EU-wide KYB entry point (with France and Finland national registers bundled in), which implicitly routes an agent away from narrower siblings. It does not explicitly state when to prefer a country-specific tool, and there are no stated prerequisites beyond the VAT number.

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