Skip to main content
Glama

Rulepass e-invoicing

Check an EU VAT number (VIES)

lookup_vat_number
Read-only

Checks an EU VAT number in the European Commission VIES register. status: valid (with registered name and address where the country publishes them), invalid, or unavailable (national register busy; try later).

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": {
      "number": "<number>"
    },
    "name": "lookup_vat_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesVAT number with country prefix, e.g. BE0123456749 or NL123456789B01.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true and openWorldHint=true, and the description adds useful behavioral detail beyond them: it enumerates status outcomes, notes that valid results may include registered name and address where published, and explains unavailable as a busy national register with retry guidance. It does not mention rate limits or timeout behavior, so it falls short of a 5.

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?

The description is two sentences, front-loaded with the core action and followed by a compact status taxonomy. Every sentence adds useful information, with no visible repetition or 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?

For a simple one-parameter lookup with read-only/open-world annotations and no output schema, the description covers the essential behavior: what register is queried, what status values mean, when valid data may include name and address, and what to do when the national register is unavailable. Nothing material is missing for an agent to invoke it correctly.

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%, and the single number parameter is already fully documented with country-prefixed examples in the schema. The description adds the VIES/EU context but does not provide additional syntax or formatting rules beyond what the schema supplies, so baseline 3 is appropriate.

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?

The description states a specific verb and resource: checks an EU VAT number in the European Commission VIES register. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as lookup_peppol_participant or check_invoice.

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 purpose: use it to validate an EU VAT number against VIES. However, the description gives no explicit when-to-use guidance, prerequisites, or alternatives for related tools, so the agent must infer context.

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.