Skip to main content
Glama

Validate EU/XI B2B VAT ID & VIES Reverse-Charge State

revclamp_validate_eu_vat_vies
Read-onlyIdempotent

Normalize EU-27 and Northern Ireland (XI) B2B VAT identifiers (including mandatory Greece ISO-3166 GR to EL prefix normalization) and evaluate cross-border 0% VAT reverse-charge eligibility, VIES consultation evidence, or MS_UNAVAILABLE circuit-breaker fulfillment hold actions. Read-only and non-destructive; supports deterministic simulation modes ('VALID', 'INVALID', 'MS_UNAVAILABLE') or real-time European Commission VIES SOAP/REST lookup ('LIVE'). Returns structuredContent containing ok, mode, statelessEphemeralAudit, simulatedViesLookup, tenantId, normalizedVat, reverseChargeEligible, and viesDecision (status, action, zeroRateAllowed, consultationId). Use this tool for EU/XI VAT tax compliance; use revclamp_reconcile_b2b_net_terms for wholesale Net-15/30/60 deposit and credit-note accounting.

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": "revclamp_validate_eu_vat_vies"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoNoOptional simulation flag (boolean) for deterministic VIES gateway preset evaluation.
viesModeNo'FORMAT_ONLY' (default; pass 'LIVE' with workspace key for real-time EC VIES lookup)FORMAT_ONLY
buyerVatIdNoBuyer EU or Northern Ireland VAT registration number to normalize and validate (e.g. 'DE123456789', 'GR123456789', 'NL123456789B01', 'XI123456789', max 40 chars; runtime aliases: vatId, or buyerCountry/buyerCountryCode + vatNumber).
supplyTypeNoCross-border transaction supply category: 'GOODS' (Directive 2006/112/EC Art. 138(1) intra-Community supply, default; permitted for Northern Ireland XI under Windsor Framework) or 'SERVICES' (Directive 2006/112/EC Art. 196 B2B reverse charge; excluded from EU VIES for Northern Ireland XI).GOODS
sellerCountryNoTwo-letter EU-27 or XI member state prefix of the merchant's dispatch warehouse (e.g. 'DE', 'NL', 'FR', 'EL', 'XI'; 'GR' is automatically normalized to 'EL'; default: 'DE'; runtime alias: sellerCountryCode).DE
consultationNumberNoOptional VIES requester consultation reference number (e.g. 'WAPIAAAAW998877', max 64 chars) to attach to deterministic 'VALID' mode tax audit records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / buyerVatId / description
      Previous value: -"Required buyer EU or Northern Ireland VAT registration number to normalize and validate (e.g. 'DE123456789', 'GR123456789', 'NL123456789B01', 'XI123456789', max 40 chars)."New value: +"Buyer EU or Northern Ireland VAT registration number to normalize and validate (e.g. 'DE123456789', 'GR123456789', 'NL123456789B01', 'XI123456789', max 40 chars; runtime aliases: vatId, or buyerCountry/buyerCountryCode + vatNumber)."
    • addedInput schema / properties / demo / default
      Added value: +false
    • addedInput schema / properties / sellerCountry / default
      Added value: +"DE"
    • changedInput schema / properties / sellerCountry / description
      Previous value: -"Two-letter EU-27 or XI member state prefix of the merchant's dispatch warehouse (e.g. 'DE', 'NL', 'FR', 'EL', 'XI'; 'GR' is automatically normalized to 'EL'; default: 'DE')."New value: +"Two-letter EU-27 or XI member state prefix of the merchant's dispatch warehouse (e.g. 'DE', 'NL', 'FR', 'EL', 'XI'; 'GR' is automatically normalized to 'EL'; default: 'DE'; runtime alias: sellerCountryCode)."
    • addedInput schema / properties / viesMode / default
      Added value: +"FORMAT_ONLY"
    • changedInput schema / properties / viesMode / description
      Previous value: -"VIES evaluation mode: 'FORMAT_ONLY' (deterministic EU/XI syntax validation without consultation; local engine default), 'VALID' (deterministic active VAT simulation; cloud endpoint default), 'INVALID' (deterministic rejected VAT simulation), 'MS_UNAVAILABLE' or 'GLOBAL_MAX_CONCURRENT_REQ' (deterministic member-state outage circuit-breaker simulation), or 'LIVE' (real-time European Commission VIES lookup)."New value: +"'FORMAT_ONLY' (default; pass 'LIVE' with workspace key for real-time EC VIES lookup)"
  2. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "buyerVatId"
      -]
  3. Changed2 schema fields changed
    • addedInput schema / properties / supplyType
      Added value: +{
      +  "default": "GOODS",
      +  "description": "Cross-border transaction supply category: 'GOODS' (Directive 2006/112/EC Art. 138(1) intra-Community supply, default; permitted for Northern Ireland XI under Windsor Framework) or 'SERVICES' (Directive 2006/112/EC Art. 196 B2B reverse charge; excluded from EU VIES for Northern Ireland XI).",
      +  "enum": [
      +    "GOODS",
      +    "SERVICES"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / viesMode / description
      Previous value: -"VIES evaluation mode: 'FORMAT_ONLY' (deterministic EU/XI syntax validation without consultation), 'VALID' (deterministic active VAT simulation, default), 'INVALID' (deterministic rejected VAT simulation), 'MS_UNAVAILABLE' or 'GLOBAL_MAX_CONCURRENT_REQ' (deterministic member-state outage circuit-breaker simulation), or 'LIVE' (real-time European Commission VIES lookup)."New value: +"VIES evaluation mode: 'FORMAT_ONLY' (deterministic EU/XI syntax validation without consultation; local engine default), 'VALID' (deterministic active VAT simulation; cloud endpoint default), 'INVALID' (deterministic rejected VAT simulation), 'MS_UNAVAILABLE' or 'GLOBAL_MAX_CONCURRENT_REQ' (deterministic member-state outage circuit-breaker simulation), or 'LIVE' (real-time European Commission VIES lookup)."
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds real value beyond that: GR-to-EL prefix normalization, Windsor Framework treatment of XI, the circuit-breaker hold on MS_UNAVAILABLE, and the enumerated return fields. It falls short of 5 because the description omits two enum modes present in the schema (FORMAT_ONLY default behavior and GLOBAL_MAX_CONCURRENT_REQ), leaving those behavioral paths unexplained.

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?

Two sentences, front-loaded with the core operation and ending with an explicit sibling routing statement. The first sentence is densely packed and the return-field enumeration is long, but since there is no output schema that enumeration earns its place. Minor redundancy in restating annotation-covered properties (read-only, non-destructive).

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 compensates by naming the structuredContent fields, and all six parameters are documented. What is missing is explanation of the default FORMAT_ONLY path and the GLOBAL_MAX_CONCURRENT_REQ mode, plus any note on what the LIVE workspace key requirement implies for failure. Otherwise complete for a compliance-validation tool.

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 schema already documents every parameter including the enum values and aliases. The description restates the normalization rule and the GOODS/SERVICES distinction but adds no syntax, format, or edge-case detail beyond what the schema provides. Baseline 3 is correct when the schema carries the parameter burden.

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 states a specific compound verb (normalize + evaluate) against a precise resource (EU-27/XI B2B VAT identifiers) and names the sibling it is not (revclamp_reconcile_b2b_net_terms) with the domain that sibling owns. An agent can distinguish this tool from the accounting sibling without opening either 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?

It explicitly routes the agent: 'Use this tool for EU/XI VAT tax compliance; use revclamp_reconcile_b2b_net_terms for wholesale Net-15/30/60 deposit and credit-note accounting.' The mode enumeration in the description further tells the agent which mode to pick for simulation versus a live lookup, so the when-to-use decision is fully covered.

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.