Skip to main content
Glama

Live EU VIES VAT Registration Lookup

vat_vies_live_lookup
Read-onlyIdempotent

Live European Commission VIES lookup for EU intra-Community transactions returning active registration status, trader name/address, requestIdentifier, SHA-256 digest, and signed receipt.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "purpose": "eu_intra_community_transaction",
      "vat_number": "0417497106",
      "country_code": "BE"
    },
    "name": "vat_vies_live_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeYesRequired VIES terms declaration: eu_intra_community_transaction
vat_numberYesEU VAT number (with or without member-state prefix)
country_codeNo2-letter EU/XI member-state prefix (optional if prefixed in vat_number)
requester_vat_numberNoOptional requester VAT number for VIES consultation identifier
requester_country_codeNoOptional requester member-state code for VIES consultation identifier

Output Schema

NameRequiredDescriptionDefault
nameNo
validNo
statusNo
addressNo
provenanceNo
vat_numberNo
country_codeNo
request_identifierNo
existence_verified_at_registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety profile is covered. The description adds that it hits the live European Commission service and produces evidentiary artifacts (digest, signed receipt), which is genuinely useful context, but it says nothing about failure behavior for invalid or missing VAT numbers, rate limits, or service availability.

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?

A single dense sentence with the resource and scope front-loaded and no filler. It is slightly padded by enumerating return fields (requestIdentifier, digest, signed receipt) that the output schema already covers.

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?

For a read-only lookup with a full output schema, annotations and 100% parameter coverage, the definition is adequate but thin: it spends its words restating return values and omits how a negative result (inactive/unknown VAT) or a VIES outage is reported, which is the main uncertainty an agent faces.

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% with enum and examples present, so the schema fully documents required purpose declaration, VAT number form, and optional requester identifiers. The description adds no parameter-level meaning beyond the schema, which is the expected baseline here.

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 ('Live European Commission VIES lookup') plus the domain constraint ('EU intra-Community transactions'), which clearly separates it from format/checksum siblings like vat_mod97_check or lei_live_lookup. It stops short of explicitly naming any sibling or stating what it is not.

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 phrase 'for EU intra-Community transactions' implies the use case, but there is no explicit when-to-use/when-not-to-use guidance and no pointer to alternatives for related VAT validation tasks. An agent must infer the boundary from the framing alone.

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.