Skip to main content
Glama

Check EORI numbers

check_eori
Read-onlyIdempotent

Checks up to 10 EU EORI customs numbers (incl. XI) live in the European Commission's EOS validation service. Returns registered / not registered, and name and address where the holder agreed to publish them. GB EORI numbers are not supported.

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": {
      "eori_numbers": "<eori_numbers>"
    },
    "name": "check_eori"
  }
}

Input Schema

NameRequiredDescriptionDefault
eori_numbersYes1 to 10 EORI numbers with country code, e.g. DE1234567890123.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / eori_numbers / items / minLength
      Removed value: -1
    • addedInput schema / properties / with_receipt
      Added value: +{
      +  "description": "Optional, default false. Set true only when the user asks for a signed receipt of this check for their files.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: the check hits a live external registry, the name/address is only returned where the holder agreed to publish (so absent fields are expected, not failures), and GB numbers are out of scope. It omits error handling and rate/throughput behavior, keeping it below 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?

Three sentences, zero filler, front-loaded with what the tool does and what it returns, with the scope restriction last. Every clause carries information an agent needs.

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 two-parameter read-only lookup with no output schema, the description covers source, scope, batch limit, and return shape well enough to call correctly. Minor gaps remain around partial results and failure modes (e.g. invalid format vs not-registered), which matter for a 10-item batch.

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 the baseline is 3, but the description adds real meaning beyond the schema: the 'incl. XI' plus 'GB not supported' pair draws the exact validity boundary for values the schema only illustrates with a 'DE...' example. It says nothing about with_receipt, but that flag is fully self-documenting in the schema.

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?

The description names a specific verb and resource ('Checks ... EU EORI customs numbers'), names the authoritative source (European Commission's EOS validation service), states the batch ceiling (up to 10), and states exactly what comes back (registered/not registered plus published name and address). The resource itself (EORI vs VAT ID vs IBAN) cleanly separates it from the check_* siblings without needing to name them.

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?

It gives clear context for when this applies (live validation of EU EORI numbers against the EC service) and an explicit negative case: 'GB EORI numbers are not supported.' It does not route the agent to an alternative for the GB case or state prerequisites, so it stops short of full when/when-not/alternatives guidance.

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