Skip to main content
Glama

eori_validate

Validate up to 10 EORI customs trader IDs against the official EU EOS register or UK HMRC, returning validity plus consented trader name and address.

Instructions

EORI number validation (customs trader ID) against the official European Commission EOS register, and UK GB numbers against HMRC. Up to 10 numbers per call; returns validity plus name and address when the trader consented to publication. Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": "eori_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
eoriYesEORI number(s), comma-separated, max 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the batch cap, what is returned (validity plus name/address only when the trader consented to publication), the cost model (0.003 USDC on Base per *successful* call via x402), and the specific failure mode without a payment key (402 challenge). That is exactly the kind of behavior an agent cannot infer from the schema.

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 dense sentences, front-loaded with what is validated and against which registers, followed by capacity, return content, and cost/payment mechanics. No filler or redundant phrasing.

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?

There is no output schema, yet the description tells the agent what comes back (validity, name, address with consent caveat) and covers the payment/authorization path including the 402 outcome. For a one-parameter validation tool, nothing essential is missing.

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 the single parameter already documents comma-separated input with a max of 10. The description's 'Up to 10 numbers per call' restates the schema rather than adding new semantics (e.g., formatting rules, partial-failure behavior for a mixed batch). Adequate but not additive.

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 and resource ('EORI number validation (customs trader ID)') and names the authoritative data sources for each jurisdiction (European Commission EOS register, HMRC for UK GB numbers). An agent can distinguish this from sibling validators like gtin_validate or eu_vat purely from the description.

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 clear operational context for when this applies: customs trader ID validation, batchable up to 10 numbers per call, and the payment precondition. It does not name an alternative for related tax/company lookups (eu_vat, kyb_check_eu), but the domain is narrow enough that routing ambiguity is low.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.