Skip to main content
Glama

iva.pt — EU VAT check (VIES) and Portuguese VAT law

Validar número de IVA (VIES)

validar_iva
Read-only

Valida em tempo real um número de IVA intracomunitário de qualquer Estado-membro da UE (ou da Irlanda do Norte, XI) no sistema VIES da Comissão Europeia. Devolve se é válido e, quando o Estado-membro os disponibiliza, o nome e a morada registados. Se for indicado o número de IVA do requerente, faz a verificação qualificada e devolve o número de consulta da Comissão Europeia. Validates an EU VAT number in VIES.

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": {
      "numero": "<numero>"
    },
    "name": "validar_iva"
  }
}

Input Schema

NameRequiredDescriptionDefault
paisNoCódigo do país (opcional se o número já tiver prefixo).
idiomaNoIdioma das mensagens (predefinição: pt).
numeroYesNúmero de IVA com o prefixo do país, por exemplo PT515060445, ESB12345678, DE123456789. A Grécia usa EL.
requerenteNoOpcional: número de IVA de quem faz a consulta, para obter o número de consulta (verificação qualificada).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real value by disclosing that this is a live external VIES call, that registered name and address are returned only when the member state publishes them, and that supplying 'requerente' changes the response to include a consultation number. It stops short of covering error modes, timeouts, or availability limits of the external service.

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 front-loaded Portuguese sentences cover purpose, scope, and conditional behavior, followed by a short English gloss. The final English sentence is largely redundant with the opening, a small amount of waste in an otherwise tight definition.

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?

There is no output schema, and the description compensates by naming what is returned (validity, registered name and address when available, consultation number). Combined with the 4 fully documented parameters, an agent has enough to invoke and interpret results, though failure behavior of the external service is unaddressed.

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%, so baseline is 3, but the description adds semantics the schema does not: 'pais' is optional when the number already carries a prefix, and 'requerente' triggers a different verification mode whose output includes a consultation number. That links parameters to observable consequences rather than restating field text.

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 (validar) and resource (número de IVA intracomunitário) plus the external system used (VIES da Comissão Europeia), and scopes it to any EU member state or Northern Ireland (XI). Nothing about it overlaps with the sibling legislation-lookup tools, so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the use case explicit (real-time VAT validation) and explains the conditional path: if the caller's own VAT number is supplied, a qualified verification with a consultation number is performed. It offers no explicit when-not guidance, but with unrelated siblings (artigo_civa, artigo_riti, pesquisar_legislacao) there is no alternative to disambiguate against.

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.

Resources