Skip to main content
Glama

Check an EU VAT number in VIES

vat_check
Read-onlyIdempotent

Check whether a VAT number was valid for intra-EU transactions according to VIES, the European Commission's VAT Information Exchange System, on request_date. Results are cached for 24 hours. Use it when the user asks whether a VAT number (NIF-IVA) is valid for intra-EU trade. For a Spanish NIF, use company_by_nif to look for a company with that NIF in our registry.

Returns JSON {vat_number, country_code, number, valid, request_date, source, note}. Relay note as given: the check does not identify the holder, and a negative result says nothing about the domestic tax identifier. invalid_input true: relay tell_the_user. error vies_unavailable or vat_check_rate_limited: the check could not be made now; do not call the number valid or invalid.

Read-only. Needs the basic plan or higher: send your API key in the X-API-Key header (https://bormeapi.com/account).

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

Input Schema

NameRequiredDescriptionDefault
vat_numberYesEU VAT number with its two-letter country code, e.g. ESA28015865 or DE123456789. Spaces, dots and hyphens are ignored; GR is read as EL; a Spanish NIF without a prefix is checked as ES.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses 24-hour result caching, that the check does not identify the holder, that a negative result says nothing about the domestic tax identifier, and how per-error outcomes must be relayed. It also states the auth/plan requirement (basic plan or higher, X-API-Key header), which annotations cannot express.

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 purpose then usage then return shape, and every block carries information. It is fairly dense and slightly run-on (multiple clauses folded into single sentences), but no sentence is pure filler.

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

Completeness5/5

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

There is no output schema, and the description compensates by listing the returned JSON keys and specifying how to relay 'note' and each error state. For a one-parameter, open-world read tool, nothing an agent needs in order to call and report results correctly is missing.

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?

Schema coverage is 100% and the single parameter already documents country-code prefixes, ignored separators, GR→EL normalization, and prefixless Spanish NIF handling. The description adds little parameter-level meaning beyond noting 'request_date' semantics, so it sits at the schema baseline plus a small increment.

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 — checking whether a VAT number was valid for intra-EU transactions per VIES — plus the temporal scope ('on request_date'). It also explicitly separates the tool from the nearest sibling: 'For a Spanish NIF, use company_by_nif'.

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?

Gives an explicit trigger ('Use it when the user asks whether a VAT number (NIF-IVA) is valid for intra-EU trade') and names the alternative tool with the condition that selects it (Spanish NIF → company_by_nif). Error states are also routed (invalid_input → tell_the_user; vies_unavailable/rate_limited → do not call valid or invalid).

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.