Skip to main content
Glama

Find Legal Entity Identifier (LEI)

find_lei
Read-onlyIdempotent

Looks up a company's LEI in the GLEIF database: by LEI code (with entity status, registration status, BIC and direct and ultimate parent company) or by company name (possible matches, optionally filtered by country).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_lei"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNoA 20-character LEI code.
nameNoCompany name, if no LEI is known.
countryNoOptional two-letter country code for a name search.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / with_receipt
      Added value: +{
      +  "description": "Optional, default false. Set true only when the user asks for a signed receipt of this check for their files.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, openWorldHint and destructiveHint already declared, the description contributes real added context: it names the authoritative source (GLEIF) and discloses what each mode returns, notably that a name lookup yields 'possible matches' rather than a single definite entity, and that a code lookup returns status, BIC and parent data. It does not explain the signed-receipt cost/side effects of with_receipt, which keeps it from a 5.

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?

A single sentence that front-loads the verb, source and both modes; nothing is padded or repeated from the title, and the parentheticals each carry distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey returns, and it does list the key fields for both modes plus the source of truth. It omits edge behavior such as a not-found result or what happens when both lei and name are supplied, which is a modest gap for a four-parameter lookup tool.

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 100%, so the baseline is 3, but the description genuinely adds meaning: it clarifies that 'country' only applies to the name search path, and it ties each input mode to a different result shape (status/BIC/parents vs candidate matches). It adds no guidance beyond the schema for with_receipt.

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: looks up a company's LEI in the GLEIF database. It further names both lookup modes (by LEI code vs by company name) and the fields returned in each, which is enough for an agent to distinguish it from the validation-style siblings such as check_vat_id or find_swiss_company.

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?

The description implies the input-mode choice (use a code when you have one, otherwise search by name, with country as a name-search filter), which is useful routing guidance. However it never states when to prefer this tool over the other partner/vendor-check siblings, nor any exclusions or prerequisites, so usage 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