GlobalEntity API

Verify a VAT, EORI or LEI number

verify_identifier

Read-onlyIdempotent

Check a number at the official source: EU VAT via VIES, EORI via EU customs (EOS), LEI via GLEIF. Returns whether it is valid plus the registered name and address. valid=null means the official service could not confirm right now.

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": {
      "type": "<type>",
      "number": "<number>"
    },
    "name": "verify_identifier"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Identifier type.
`number`	Yes	The number, e.g. DK22756214 (VAT), DK22756214 (EORI) or a 20-character LEI.
`country`	No	ISO country code for a VAT number without prefix, e.g. DK.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover readOnly/openWorld/idempotent, yet the description adds real behavior: the lookup hits external official registries, returns validity plus registered name and address, and defines the tri-state 'valid=null' failure case where the upstream service could not confirm. It stops short of timeouts, rate limits, or per-registry quirks.

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 with zero filler: what it checks and where, what it returns, and how to interpret the null case. Front-loaded and easy to scan.

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?

With no output schema, the description carries the return-shape burden and does so — validity flag, registered name, address, and the null semantics. Nothing an agent needs in order to call this correctly 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%, so the baseline is 3. The description adds framing for the type enum values (which registry each maps to) but no new meaning for 'number' or 'country' beyond what the schema and its examples already state.

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 (verify/check) and resource (VAT, EORI, LEI identifiers) and names the authoritative source for each subtype (VIES, EU customs EOS, GLEIF). It is clearly distinct from rate-lookup or company-search siblings, though it never names a sibling explicitly.

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 is implied by the tool's nature — an agent knows to call this when it has an identifier to validate. But there is no explicit when-to-use / when-not, no prerequisites, and no routing against near-neighbors like get_vat_rates or resolve_company.

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

All GlobalEntity API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?