Skip to main content
Glama

Check UK EORI customs numbers with HMRC

eori
Read-only

Checks up to 10 UK EORI numbers (GB or XI followed by 12 or 15 digits) with HMRC's public check: valid or not, with the processing date. HMRC does not publish the trader's name in this check, so it is null. An HMRC outage is a 503, not charged, never 'invalid'. EU EORI numbers are refused with a 400 in this version. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls 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": {
      "eori": "<eori>"
    },
    "name": "eori"
  }
}

Input Schema

NameRequiredDescriptionDefault
eoriYesOne UK EORI number, or up to 10 separated by commas, e.g. GB123456789000

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
sourceNo
resultsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses non-obvious behavior: the trader name is null because HMRC does not publish it, an HMRC outage surfaces as 503 rather than a false 'invalid', and EU numbers are refused with 400. It also states the billing model (per successful call, x402, failed calls free), which is exactly the kind of operational context annotations cannot carry.

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?

Front-loaded with the core operation and input format, then result shape, then failure modes, then price. Every sentence conveys a distinct, decision-relevant fact with no restatement of the title or padding.

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 tool with an output schema, this covers everything an agent needs: accepted input forms, expected result fields (validity plus processing date, null name), and error/pricing semantics for the failure paths. Nothing essential to correct invocation is missing.

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 already 100%, so the baseline is 3, but the description adds real constraints the schema only hints at: the GB/XI prefix and the 12-or-15-digit length rule, plus the 10-number comma-separated maximum. That materially helps an agent pre-validate input before calling.

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 opens with a specific verb and resource: 'Checks ... UK EORI numbers ... with HMRC's public check', and immediately bounds the scope to GB/XI prefixed numbers. The explicit exclusion of EU EORI numbers sharpens the boundary against adjacent customs/company tools, so an agent can identify the tool's remit without opening the 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?

Usage context is clear: batch up to 10 numbers, separator convention, and what happens when EU numbers are submitted (400 refusal, this version). It stops short of naming an alternative tool for EU checks or for the broader customs-tariff queries that a sibling like tariff_uk might serve, so the when-to-use-this-vs-that routing is implied rather than explicit.

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