Skip to main content
Glama

Validate EU VAT number (VIES)

validate_vat_eu

Use this when you need to confirm that an EU VAT number is actually registered for intra-community trade (B2B invoicing, reverse charge, supplier onboarding). Checks the format locally, then queries the European Commission VIES service live and returns valid, the registered name and address when the member state discloses them, the request date and an optional consultation number. Supported: the 27 EU member states plus XI (Northern Ireland): AT, BE, BG, CY, CZ, DE, DK, EE, EL, ES, FI, FR, HR, HU, IE, IT, LT, LU, LV, MT, NL, PL, PT, RO, SE, SI, SK, XI. Non-EU countries return UNSUPPORTED_COUNTRY; VIES outages return SOURCE_UNAVAILABLE. Neither is charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "validate_vat_eu"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoBatch mode: up to 500 items, each with the same fields as a single call. Omit when validating a single value through the top-level fields.
vatNumberNoVAT number with or without the country prefix, spaces or dots, e.g. "IE6388047V", "DE 123 456 789", "ESB12345674".
countryCodeNoTwo-letter VIES country code of the VAT number: the 27 EU member states plus XI (Northern Ireland). Greece is "EL" ("GR" accepted).
requesterVatNumberNoOptional: your own VAT number (without country prefix).
requesterCountryCodeNoOptional: your own VIES country code. Together with requesterVatNumber, VIES returns a consultation number as proof of the check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load and does substantial work: it discloses the two-stage local-then-live-remote check, names the failure modes (UNSUPPORTED_COUNTRY, SOURCE_UNAVAILABLE) and states they are not charged. It does not cover latency, rate limits, or retry behavior for the external VIES dependency.

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?

Front-loaded with the 'Use this when' trigger, followed by returns and error behavior. The 28-code country enumeration is long and duplicates what the countryCode schema description already lists, which is the main redundancy.

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 annotations and no output schema, the description supplies the return shape (valid flag, name/address, request date, consultation number) and error codes, which an agent needs. Batch-mode mechanics and how the requester fields unlock the consultation number are only covered in the schema, leaving a small gap.

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 all five parameters, including nested batch items and the optional requester fields, are already documented. The description's supported-country list reinforces countryCode semantics and mentions the consultation number, but adds no syntax or format guidance beyond the schema.

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?

States a specific verb and resource: confirm an EU VAT number is registered for intra-community trade, via a local format check plus a live VIES lookup. The EU/VIES scope implicitly separates it from the generic validate_tax_id and from get_vat_rates, but no sibling is named explicitly.

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 opening clause gives concrete triggering scenarios (B2B invoicing, reverse charge, supplier onboarding), which is clear usage context. It stops short of explicit exclusions or naming an alternative tool for non-EU VAT or rate lookups.

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.