EU Business & VAT Checker

Look up a Legal Entity Identifier

find_company_lei

Read-onlyIdempotent

Use this when the user asks for the Legal Entity Identifier (LEI) of a company, including a KYB or vendor onboarding check, for example "what is the LEI of Siemens AG?", "whose LEI is W38RGI023J3WT1HWRP32?" or "is the LEI of this German company still active?". Pass the company name (and a country code to narrow it) or the 20-character LEI. Returns each entity's LEI, legal name, status, legal form code, country and city, national registration number and the LEI's renewal dates. Sole proprietors are left out. Do not use it to find a private person, for companies that have no LEI (most small businesses), or for financial or credit information.

Input Schema

Name	Required	Description
`lei`	No	A 20-character Legal Entity Identifier to look up directly.
`name`	No	Company or organisation name to search for. Send either name or lei.
`limit`	No	Most entities to return. Default 5.
`country`	No	Two-letter country of the legal address to narrow a name search, for example DE.

Output Schema

Name	Required	Description	Default
`note`	No
`notice`	Yes
`source`	Yes
`entities`	Yes
`totalMatches`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds real behavioral context beyond them: it enumerates returned fields, notes that status/renewal dates are included, and discloses that sole proprietors are excluded from results.

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?

The description is dense but front-loaded: it leads with the core purpose, then examples, then exclusions. The three example queries take space but each illustrates a distinct mode (name lookup, LEI reverse lookup, status check), so they mostly earn their place.

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 an output schema present and rich annotations, the description need not explain return values, yet it still summarizes them helpfully. Combined with usage conditions and exclusions, an agent has everything needed to call this tool correctly.

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 schema already documents all four parameters including the name/lei choice and country narrowing. The description's 'pass the company name (and a country code to narrow it) or the 20-character LEI' largely restates what the schema says, adding little beyond the baseline.

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 states a specific verb and resource ('find the Legal Entity Identifier (LEI) of a company') and scopes it with concrete example queries. It clearly distinguishes itself from siblings like lookup_company_registry and check_vat_number by centering on the LEI and even the reverse lookup by LEI string.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use triggers (user asks for an LEI, KYB or vendor onboarding) and explicit when-not conditions (private persons, companies with no LEI such as most small businesses, financial/credit information). The example queries remove ambiguity about the intended invocation.

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

All EU Business & VAT Checker 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.