Skip to main content
Glama

lei_lookup

Look up Legal Entity Identifiers in the official GLEIF register by LEI or legal name with optional country filtering to retrieve entity status, addresses, parent relationships, and BIC.

Instructions

Legal Entity Identifier lookup from the official GLEIF register: by LEI (with ISO 17442 checksum check) or by legal-name search with optional country. Returns legal name, status, legal form, jurisdiction, legal and HQ addresses, registration status/renewal, BIC, direct and ultimate parents. Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": "lei_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNo20-char LEI
maxNo1-20
nameNoLegal name search (alternative)
countryNoISO alpha-2 filter for name search
relationshipsNotrue/false, default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does well on the critical points: it discloses the 0.003 USDC per-successful-call cost via x402 and that a missing payment key yields a 402 challenge, plus the checksum validation behavior and the returned field set. It does not cover rate limits, whether failed lookups are billed, or error behavior for an invalid LEI, so it is strong but not complete.

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?

Front-loaded with what the tool does, then the returned fields, then the payment caveat. Dense but every clause carries information; the payment sentence is placed at the end where an agent deciding to call might skim past it.

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 no output schema, the description usefully enumerates the returned fields and the payment failure mode, which is what an agent needs before calling. Minor gaps remain around name-search pagination ('max') and invalid-LEI error behavior.

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 adds real meaning beyond it by clarifying that lei and name are mutually exclusive entry paths and that country only applies to name search. The 'max' and 'relationships' parameters are left unaddressed beyond their terse schema strings.

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 ('Legal Entity Identifier lookup'), names the authoritative source (GLEIF register), and distinguishes two distinct operating modes (lookup by LEI vs. legal-name search). An agent immediately knows what data comes back and how the two input paths differ.

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?

Explains how to pick between the two modes: LEI path with ISO 17442 checksum validation, or name search with an optional country filter. Clear context, but no explicit exclusions or comparison against related siblings such as fr_company or kyb_check_eu, so the agent must infer when this register is the right source.

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