Skip to main content
Glama
eu-kyb-mcp

eu-kyb-mcp

by mastermabel

Validate EU VAT number (VIES)

check_eu_vat
Read-only

Validate EU VAT identification numbers against the European Commission's VIES service to confirm validity and retrieve registered name and address when disclosed.

Instructions

Validate an EU VAT identification number against the European Commission's VIES service. Returns validity and, where the member state discloses them, registered name and address.

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_number": "<vat_number>"
    },
    "name": "check_eu_vat"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_numberYesVAT number, with or without country prefix, e.g. DE123456789
country_codeNoEU member state code (e.g. DE, FR, EL for Greece, XI for Northern Ireland). Optional if vat_number has a prefix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered structurally. The description adds genuinely new behavior: it discloses that only validity is guaranteed, while registered name and address are returned conditionally 'where the member state discloses them' — important since no output schema exists. It does not mention the well-known VIES caveat that service outages can return unavailability/invalid results, nor any rate limits.

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?

Two tight sentences with zero filler; the verb and resource come first, and the return-value caveat follows. Every sentence earns its place.

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 two-parameter, read-only lookup with no output schema, the description covers what the tool does and the partial nature of the response. Missing only operational context (rate limits, VIES downtime behavior) that an agent would benefit from when interpreting a negative result.

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%, and the schema already documents both vat_number (with prefix example) and country_code (including EL for Greece and XI for Northern Ireland). The description adds no meaning beyond that, 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?

States a specific verb ('Validate') and resource ('EU VAT identification number') and names the authoritative backend (European Commission's VIES service). This is clearly distinct from siblings like check_email_domain, lookup_lei, and request_verification_report without needing to open 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 Guidelines3/5

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

The purpose implies usage (checking VAT validity for a given number), but there is no explicit when-to-use/when-not guidance, no mention of the alternative tools, and no statement about preconditions such as needing a country prefix or when to prefer the optional country_code parameter.

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