Skip to main content
Glama

vies_gleif_kyb_verify

Read-onlyIdempotent

[Live official EU/Global registry lookup. Read-only, non-destructive, side-effect free]. Verifies European VAT validity via official VIES API, extracts official registered legal company name and address, queries GLEIF for Legal Entity Identifier (LEI) corporate hierarchy, and screens against consolidated EU, OFAC and UN sanctions lists. Usage: Use this tool when you already have a European VAT number to verify against statutory registries and check sanctions. If you only have a company website URL and need to discover its VAT number from legal footers, use 'b2b_tech_profiler' instead. Returns: JSON object with { isValid: boolean, countryCode: string, vatNumber: string, name: string, address: string, lei: string | null, sanctionsCheck: { isSanctioned: boolean, matches: array }, verificationTimestamp: string }.

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": {
      "countryCode": "<countryCode>",
      "vatNumber": "<vatNumber>"
    },
    "name": "vies_gleif_kyb_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
vatNumberYesVAT number without country prefix (e.g. 01234567890)
companyNameNoOptional company name for cross-check and LEI lookup
countryCodeYes2-letter EU country code (e.g. IT, DE, FR, ES)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description reinforces this with "Live official EU/Global registry lookup" and "side-effect free," plus it discloses the return payload shape and a verificationTimestamp. It stops short of behavioral context that matters for a live external-registry call, such as rate limiting, upstream VIES/GLEIF outage behavior, or what happens when the registry is unreachable — gaps worth noting for a tool chaining three external services.

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 description is front-loaded with purpose, then clearly segmented into "Usage" and "Returns" blocks, and every clause maps to a real capability. The bracketed "[Read-only, non-destructive, side-effect free]" restates what the annotations already declare, which is mild duplication, and the "Returns" block is somewhat dense but earns its place given there is no output schema.

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 three-external-service verification tool with no output schema, the description supplies the return field list (isValid, countryCode, vatNumber, name, address, lei, sanctionsCheck with matches, verificationTimestamp), which is exactly the missing context. Combined with the stated preconditions and the alternative tool, an agent has enough to call this correctly.

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 description coverage is 100%, so the three parameters (vatNumber without prefix, optional companyName, 2-letter countryCode) are already documented with examples. The description adds only indirect meaning — that the company name feeds a cross-check and LEI lookup — without format or edge-case detail beyond the schema, so the baseline 3 applies.

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 description opens with a specific verb-and-resource statement ("Verifies European VAT validity via official VIES API") and enumerates the three concrete operations: VIES VAT check, GLEIF LEI hierarchy lookup, and sanctions screening. It also names a sibling-style alternative ("b2b_tech_profiler") so the agent can separate this tool from a website-to-VAT discovery tool without opening any schema.

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?

The "Usage" sentence states the precondition explicitly ("when you already have a European VAT number") and gives a clear exclusion plus the alternative to use instead when only a website URL is available. This is the when/when-not/alternative pattern, so nothing is left to inference.

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.

Resources