Skip to main content
Glama

UK company & compliance data

Global LEI Register: LEI lookup

gleif__lookup
Read-onlyIdempotent

Legal name, addresses, jurisdiction, legal form, status and registration for one LEI. Free within the daily allowance, then $0.003 USDC per call via x402.

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": {
      "lei": "<lei>"
    },
    "name": "gleif__lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYes20-character Legal Entity Identifier

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new operational context that annotations cannot express: the free daily allowance and the $0.003 USDC per-call charge via x402, which matters for an agent deciding whether to spend a call.

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?

Two dense sentences: the returned fields first, then the cost model. No filler, no restatement of the title, and the most decision-relevant information (what you get, what it costs) is front-loaded.

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?

An output schema exists, so return structure need not be described, and annotations carry the safety semantics. For a one-parameter identifier lookup the description covers purpose, payload and cost adequately; only the routing against neighbouring GLEIF endpoints 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 coverage is 100% — the single 'lei' parameter is fully documented as a 20-character Legal Entity Identifier. The description adds no format detail, truncation rules, or handling for malformed LEIs beyond what the schema already states, so the baseline 3 applies.

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?

The description states exactly what comes back for a single LEI — legal name, addresses, jurisdiction, legal form, status and registration — which is more concrete than a generic 'lookup'. The phrase 'for one LEI' implicitly separates it from query-based siblings like gleif__search, gleif__fuzzy and gleif__autocomplete, though those siblings are never named.

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 only implied: taking a single LEI signals an exact-identifier lookup rather than a name search, so an agent can infer it should use search/autocomplete first if it lacks an LEI. No explicit when-to-use, when-not-to-use, or named alternative is given.

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