Skip to main content
Glama

Get Lei

get_lei
Read-onlyIdempotent

Fetch the full Level 1 LEI record for a legal entity. Returns legal name, registered address, headquarters address, entity category, legal form, registration authority, LEI registration status (ISSUED / LAPSED / RETIRED / ...), jurisdiction, parent LEI (if any), and timestamps. Accepts a company NAME as well as a 20-character LEI, a name is resolved against the registry here and the match is echoed back as resolved_from_name. Answers "is this company's LEI still active or has it lapsed" and "where is this entity registered".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lei": "Wirecard AG"
    },
    "name": "get_lei"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYes20-character LEI code (e.g. "HWUPKR0MPOU8FGXBT394") OR the company NAME (e.g. "Wirecard AG"), a name is resolved here automatically and the match is echoed back as resolved_from_name. Pass the name whenever that is what you were given; do not construct an LEI. A guessed 20-character code that happens to exist belongs to SOME OTHER COMPANY, and the record comes back looking perfectly valid, asking about Wirecard AG with a made-up code returned Baader Bank's registration, with nothing in the response to show it was the wrong entity.

Output Schema

NameRequiredDescriptionDefault
bicYesBank Identifier Codes
leiYes20-character LEI code
isinsYesISIN codes
categoryYesEntity category
gleif_urlYesDirect link to GLEIF record
legal_formYesLegal form ID or description
legal_nameYesOfficial legal entity name
last_updateYesISO date of last update
other_namesYesAlternative names for the entity
jurisdictionYesISO jurisdiction code
managing_louYesManaging Local Operating Unit
next_renewalYesISO date of next renewal
entity_statusYesEntity status (ACTIVE, LAPSED, etc.)
legal_addressYesLegal address of entity
registered_asNoThe company's own id in its national business register (e.g. Companies House number 00041424, Norwegian orgnr 923609016), whitespace stripped so it joins. Null when GLEIF publishes no id, and withheld for sole proprietors. Pair it with registration_authority: an id is only unique within its register.
registration_statusYesRegistration status
headquarters_addressYesHeadquarters address of entity
initial_registrationYesISO date of initial registration
registration_authorityNoGLEIF Registration Authority code for the register that registered_as belongs to: RA000585 = UK Companies House, RA000189 = INSEE Sirene, RA000413 = Japan NTA, RA000472 = Brønnøysund. RA999999 is GLEIF's "other / not applicable" sentinel and comes with no registered_as.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lei / description
      Previous value: -"20-character LEI code (e.g. \"HWUPKR0MPOU8FGXBT394\") OR the company NAME (e.g. \"Wirecard AG\") — a name is resolved here automatically and the match is echoed back as resolved_from_name. Pass the name whenever that is what you were given; do not construct an LEI. A guessed 20-character code that happens to exist belongs to SOME OTHER COMPANY, and the record comes back looking perfectly valid — asking about Wirecard AG with a made-up code returned Baader Bank's registration, with nothing in the response to show it was the wrong entity."New value: +"20-character LEI code (e.g. \"HWUPKR0MPOU8FGXBT394\") OR the company NAME (e.g. \"Wirecard AG\"), a name is resolved here automatically and the match is echoed back as resolved_from_name. Pass the name whenever that is what you were given; do not construct an LEI. A guessed 20-character code that happens to exist belongs to SOME OTHER COMPANY, and the record comes back looking perfectly valid, asking about Wirecard AG with a made-up code returned Baader Bank's registration, with nothing in the response to show it was the wrong entity."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / registered_as
      Added value: +{
      +  "description": "The company's own id in its national business register (e.g. Companies House number 00041424, Norwegian orgnr 923609016), whitespace stripped so it joins. Null when GLEIF publishes no id, and withheld for sole proprietors. Pair it with registration_authority: an id is only unique within its register.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / registration_authority
      Added value: +{
      +  "description": "GLEIF Registration Authority code for the register that registered_as belongs to: RA000585 = UK Companies House, RA000189 = INSEE Sirene, RA000413 = Japan NTA, RA000472 = Brønnøysund. RA999999 is GLEIF's \"other / not applicable\" sentinel and comes with no registered_as.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "lei": "5493001KJTIIGC8Y1R12"
      -  }
      -]New value: +[
      +  {
      +    "lei": "Wirecard AG"
      +  },
      +  {
      +    "lei": "5493001KJTIIGC8Y1R12"
      +  }
      +]
    • changedInput schema / properties / lei / description
      Previous value: -"20-character LEI code"New value: +"20-character LEI code (e.g. \"HWUPKR0MPOU8FGXBT394\") OR the company NAME (e.g. \"Wirecard AG\") — a name is resolved here automatically and the match is echoed back as resolved_from_name. Pass the name whenever that is what you were given; do not construct an LEI. A guessed 20-character code that happens to exist belongs to SOME OTHER COMPANY, and the record comes back looking perfectly valid — asking about Wirecard AG with a made-up code returned Baader Bank's registration, with nothing in the response to show it was the wrong entity."
  4. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "lei": "5493001KJTIIGC8Y1R12"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "bic": {
      +      "description": "Bank Identifier Codes",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "category": {
      +      "description": "Entity category",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "entity_status": {
      +      "description": "Entity status (ACTIVE, LAPSED, etc.)",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "gleif_url": {
      +      "description": "Direct link to GLEIF record",
      +      "type": "string"
      +    },
      +    "headquarters_address": {
      +      "description": "Headquarters address of entity",
      +      "properties": {
      +        "city": {
      +          "description": "City name",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "country": {
      +          "description": "ISO country code",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "lines": {
      +          "description": "Address lines",
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "postal_code": {
      +          "description": "Postal code",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "region": {
      +          "description": "Region or state",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "initial_registration": {
      +      "description": "ISO date of initial registration",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "isins": {
      +      "description": "ISIN codes",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "jurisdiction": {
      +      "description": "ISO jurisdiction code",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "last_update": {
      +      "description": "ISO date of last update",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "legal_address": {
      +      "description": "Legal address of entity",
      +      "properties": {
      +        "city": {
      +          "description": "City name",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "country": {
      +          "description": "ISO country code",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "lines": {
      +          "description": "Address lines",
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "postal_code": {
      +          "description": "Postal code",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "region": {
      +          "description": "Region or state",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "legal_form": {
      +      "description": "Legal form ID or description",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "legal_name": {
      +      "description": "Official legal entity name",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "lei": {
      +      "description": "20-character LEI code",
      +      "type": "string"
      +    },
      +    "managing_lou": {
      +      "description": "Managing Local Operating Unit",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "next_renewal": {
      +      "description": "ISO date of next renewal",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "other_names": {
      +      "description": "Alternative names for the entity",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "registration_status": {
      +      "description": "Registration status",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "lei",
      +    "legal_name",
      +    "other_names",
      +    "jurisdiction",
      +    "category",
      +    "legal_form",
      +    "entity_status",
      +    "registration_status",
      +    "initial_registration",
      +    "last_update",
      +    "next_renewal",
      +    "managing_lou",
      +    "legal_address",
      +    "headquarters_address",
      +    "bic",
      +    "isins",
      +    "gleif_url"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description adds genuine value beyond those flags: the full field set returned, status enumeration values, the resolved_from_name echo, and the fact that name lookup is resolved against the registry on this call.

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?

It is front-loaded with the core action and then the return payload, which is the right order for an agent scanning for relevance. The field list is long but each item is informative; the closing question-framing sentence is useful but slightly redundant with the status list already given.

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?

With one required parameter, full schema coverage, and an output schema, little is left to explain, and the description still covers input flexibility, return shape, and the practical status question. The main residual gap is that it never mentions behavior on no-match or ambiguous name resolution, which matters for a name-resolving lookup.

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 schema's own parameter description is already rich, including the warning against fabricating a 20-character code. The description only restates that a name or LEI is accepted, which duplicates the schema rather than adding new meaning, so the baseline of 3 applies.

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: 'Fetch the full Level 1 LEI record for a legal entity', and enumerates the fields returned, which implicitly scopes it apart from relationship, hierarchy, or screening siblings. An agent can immediately tell this is a single-entity record fetch, not a search or traversal.

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?

It gives clear context for when to reach for this tool by phrasing the questions it answers ('is this company's LEI still active or has it lapsed', 'where is this entity registered') and by stating that a name is resolved here so a prior search is unnecessary. It stops short of naming alternatives such as search_lei or lei_hierarchy_tree or stating when not to use it.

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.