Skip to main content
Glama

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

Verify EU EORI number (EC EOS)

verify_eori
Read-onlyIdempotent

Validate an EU EORI (customs Economic Operators Registration and Identification) number, e.g. 'SE5560360793', 'DE1234567890123', against the official European Commission EOS service. Use for import/export, customs declarations and freight-forwarder onboarding. Returns valid/invalid and trader name/address only when the trader consented to publication. UK (GB) EORIs are not in EOS (HMRC checks those); XI EORIs are.

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": "<eori>"
    },
    "name": "verify_eori"
  }
}

Input Schema

NameRequiredDescriptionDefault
eoriYesEORI number with country prefix, e.g. 'SE5560360793'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / eori / description
      Added value: +"EORI number with country prefix, e.g. 'SE5560360793'."
  2. 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/openWorld/idempotent/non-destructive, and the description adds genuinely non-derivable behavior: the return surface (valid/invalid plus trader name/address) and the crucial caveat that name/address only appear when the trader consented to publication, so missing data must not be read as invalid. The ellipsis in 'XI EORIs are' is clumsy, and nothing is said about failure modes or rate limits.

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?

Front-loaded with the verb and resource, then use cases, then the return caveat — a sensible order with little filler. The final sentence is elliptical ('XI EORIs are') and would read better as a complete clause.

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 single-parameter, read-only lookup with no output schema, the description supplies exactly what structured fields cannot: what comes back, why fields may be absent, and which jurisdiction codes are out of scope. An agent can call this correctly and interpret a sparse response without further documentation.

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?

With one parameter at 100% schema description coverage, the schema already defines the field and its country-prefix format. The description's additional examples ('SE5560360793', 'DE1234567890123') merely echo the schema example rather than adding new constraints.

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 ('Validate an EU EORI ... number') and names the authoritative upstream system (European Commission EOS), with concrete format examples. It does not name the obvious sibling (verify_eori_batch) or clarify when to use single vs. batch, relying instead on the explicit 'EU EORI' scoping to separate it from verify_vat.

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?

Gives concrete usage contexts ('import/export, customs declarations and freight-forwarder onboarding') and a scope exclusion ('UK (GB) EORIs are not in EOS'), which prevents a whole class of misdirected calls. It stops short of naming an alternative tool for GB/HMRC lookups, so the exclusion tells the agent what not to expect but not where to go instead.

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.