Skip to main content
Glama

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

Verify up to 100 EU EORI numbers

verify_eori_batch
Read-onlyIdempotent

Validate up to 100 EU EORI numbers in one call via the official EC EOS service (customs / import-export KYB).

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": {
      "eoris": "<eoris>"
    },
    "name": "verify_eori_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
eorisYesList of up to 100 EORI numbers with country prefix.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / eoris / description
      Added value: +"List of up to 100 EORI numbers with country prefix."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and openWorld, so the bar is lower. The description adds two things annotations cannot: the data comes from the official EC EOS service (explaining the openWorld flag and trust level) and the hard cap of 100 per call. It does not say how partial or invalid results are handled, which is the main remaining behavioral gap.

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?

One sentence, front-loaded with the verb and the batch limit, with the service provenance and use case in a compact parenthetical. Nothing is padding.

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?

For a one-parameter batch validation tool with an output schema, the description covers scope, source, and limit adequately. What is missing is failure semantics (what happens when some EORIs are invalid or malformed) and any rate or cost implication of hitting an external EC service.

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?

Single parameter with 100% schema description coverage that already states 'list of up to 100 EORI numbers with country prefix'. The description adds no syntax, format, or validation detail beyond what the schema and title already convey, so 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 (validate), a specific resource (EU EORI numbers), a batch scope (up to 100 in one call), and the authoritative source (official EC EOS service). The batch framing plus the 'one call' phrasing clearly separates it from the single-number verify_eori sibling without needing to name it.

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 context is implied rather than stated: customs / import-export KYB, batch of up to 100. It never says when to prefer this over verify_eori for a handful of numbers, nor when to pick verify_batch or kyb_check instead, and gives no prerequisites for the EORI format.

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.