Skip to main content
Glama

eu_vat

Validate an EU VAT number against the European Commission VIES service and return normalised results: validity, registered name and address. Requires a 2-letter country prefix.

Instructions

EU VAT number validation against the European Commission VIES service, with normalised output (valid, name, address). Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault
vatYesVAT number with 2-letter country prefix, e.g. FR40303265045

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose notable traits: an external VIES dependency, a per-successful-call price of 0.003 USDC on Base, and the x402 402-challenge behavior without a key. It still leaves out error semantics (does an invalid VAT return valid=false or an error?), timeouts, and whether failed lookups are billed.

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?

Three sentences, front-loaded with what the tool does, then the output, then the commercial/payment constraint. No filler and nothing repeated from the schema.

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 one-parameter validation call with no output schema, the definition covers purpose, source, output fields, cost, and the payment failure mode — enough to invoke it correctly. The main residual gap is how a non-VIES-valid number is surfaced (response field vs. error).

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?

The single parameter is fully documented in the schema at 100% coverage, including the 2-letter country prefix and an example. The description adds only the output shape ('valid, name, address') and no further input semantics, so the schema is doing the work.

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 and resource ('EU VAT number validation') plus the authoritative source ('European Commission VIES service'), which cleanly separates it from the other validator siblings such as eori_validate or ch_uid. An agent knows exactly what is being checked and against what.

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?

Usage is implied by the resource name (use it to check an EU VAT number), and the description does explain the payment precondition and the 402 fallback. However, it never says when to prefer this over sibling validators or what to do if the caller lacks a payment key beyond noting the challenge is returned.

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