Skip to main content
Glama

EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)

Verify up to 100 EU VAT numbers

verify_batch
Read-onlyIdempotent

Validate up to 100 EU VAT numbers in one call via VIES (supplier/customer list cleanup, onboarding, invoice runs). Same per-item result as verify_vat; items with member_state_unavailable should be retried later (GB items stay member_state_unavailable until HMRC live access is granted; they are not charged).

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": {
      "vats": "<vats>"
    },
    "name": "verify_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
vatsYesList of up to 100 VAT numbers with country prefix; extra items are ignored.
requesterNoOptional: your own EU VAT number, so VIES returns consultation numbers as audit proof.HU33119856

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / requester / description
      Added value: +"Optional: your own EU VAT number, so VIES returns consultation numbers as audit proof."
    • addedInput schema / properties / vats / description
      Added value: +"List of up to 100 VAT numbers with country prefix; extra items are ignored."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, but the description adds material behavior they cannot express: partial-failure semantics per item, the retry-later rule for member_state_unavailable, the GB/HMRC access caveat, and the billing fact that unavailable items are not charged. Cost and failure-mode disclosure is exactly the value-add expected beyond structured fields.

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?

Three sentences, front-loaded with the core action and scope, with use cases and retry rules following. The parentheticals are dense but each carries real information; nothing is filler.

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, return values need no explanation, and the description covers batch limits, provider, partial failure, retry and cost. Minor gaps remain: no statement of rate limits or what a malformed VAT number does to the rest of the batch.

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%, so both 'vats' and 'requester' are already documented, including the 100-item cap and the extra-items-ignored rule. The description repeats the batch limit but adds no new meaning about the audit-proof 'requester' parameter, so the baseline 3 applies.

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, resource, scale and backend: 'Validate up to 100 EU VAT numbers in one call via VIES.' It also explicitly ties itself to the single-item sibling ('Same per-item result as verify_vat'), so an agent can separate batch from single-item verification without opening either 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?

Names concrete usage contexts (supplier/customer list cleanup, onboarding, invoice runs) and gives retry guidance for member_state_unavailable items. It stops short of an explicit routing rule such as 'for one VAT number use verify_vat', leaving the single-vs-batch choice to be inferred from the 100-item limit.

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.