Skip to main content
Glama

verify_eu_vat_vies

Validate an EU VAT ID against the European Commission VIES registry to confirm registration status before invoicing or cross-border transactions.

Instructions

Validate any EU 27-country VAT ID against the European Commission VIES registry.

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

Input Schema

NameRequiredDescriptionDefault
vatYesEU VAT number with country prefix, e.g. CZ00094943

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the meaningful behavioral fact that validation happens against a live external registry (VIES), but says nothing about network dependencies, registry downtime, or what an invalid/unknown result looks like.

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?

One sentence with zero filler; the scope (EU 27) and the source (VIES) are both front-loaded where an agent will read them first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a one-parameter lookup, but with no output schema the description never indicates what comes back - bare validity, or a VIES response with trader name and address - and gives no guidance on handling invalid input or registry errors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single required parameter with 100% schema description coverage, including a concrete example format ('CZ00094943'). The description's 'country prefix' phrasing reinforces the same constraint, so the schema already does the work and the description need add little.

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'), a precisely scoped resource ('any EU 27-country VAT ID'), and the authoritative source ('European Commission VIES registry'). This is unambiguously distinct from the sibling tools (IBAN validation, company KYB, exchange rates) without needing to name them.

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 scope 'any EU 27-country VAT ID' implies when the tool applies, but there is no explicit when-to-use/when-not guidance, no mention of what to do for non-EU VAT IDs, and no reference to alternatives such as the company KYB tool for deeper checks.

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