Skip to main content
Glama

Check EU VAT numbers

check_vat_numbers
Read-onlyIdempotent

Use this when the user asks for a vat number check, vies vat validation, or eu vat number lookup with dated XLSX and CSV logs. Checks 1 to 100 EU or XI VAT numbers against published structures and live VIES; no national checksum test. Do not use for deciding whether reverse charge applies.

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": {
      "numbers": "<numbers>"
    },
    "name": "check_vat_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
numbersYesThe VAT numbers with country prefixes, 1 to 100 items of 4 to 40 characters; for example ["IE6388047V", "fr 40 303265045"].
requester_vatNoYour own EU business VAT number with country prefix for consultation numbers; for example IE6388047V. Leave out to check without requester details.
default_countryNoCountry code for a number without a prefix; for example IE. Use EL for Greece.

Output Schema

NameRequiredDescriptionDefault
rowsYes
summaryYes
warningsYes
downloadsYes
availabilityYes
retrievedUtcYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds behavior the annotations cannot: batch size cap of 1-100, that validation hits live VIES (implying external latency/failure modes) and that no national checksum test is performed. It omits whether results include consultation numbers when requester_vat is supplied, and the 'dated XLSX and CSV logs' phrase is left unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger condition, which is good, but the phrase 'or eu vat number lookup with dated XLSX and CSV logs' reads as keyword stuffing and its meaning (dated log export? logging of results?) is never clarified. The sentences are compact yet one clause is wasted on unexplained jargon.

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?

With an output schema present and full parameter documentation, the description carries the right load: what is validated, against what, at what scale, and what is out of scope. The main residual gap is the effect of supplying requester_vat (consultation numbers) and the ambiguous log-format wording.

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 each parameter is documented in the schema with formats and examples, so the baseline applies. The description only echoes the 1-100 bound on numbers and adds nothing about requester_vat (which changes the returned artefact) or default_country.

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 — checks 1 to 100 EU or XI VAT numbers against published structures and live VIES — and adds the important scope qualifier 'no national checksum test'. It does not name or contrast with the sibling check_vies_availability, so the agent must infer that availability vs. validation are different concerns.

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 concrete trigger conditions (user asks for a vat number check, vies vat validation, eu vat number lookup) and an explicit exclusion ('Do not use for deciding whether reverse charge applies'). Both when-to-use and when-not-to-use are present, which is rare and genuinely routing-relevant.

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