Skip to main content
Glama

Live GLEIF LEI & Parent Consolidation Lookup

lei_live_lookup
Read-onlyIdempotent

Live GLEIF v1 API lookup returning entity status, legal address, LOU registration, direct/ultimate parent relationships, SHA-256 payload digest, and signed receipt.

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": "506700GE1G29325QX363"
    },
    "name": "lei_live_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYes20-character ISO 17442 Legal Entity Identifier

Output Schema

NameRequiredDescriptionDefault
validNo
entityNo
statusNo
parentsNo
provenanceNo
registrationNo
existence_verified_at_registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds that this is a live external v1 API call and that results carry a SHA-256 payload digest and signed receipt, which is useful integrity context, but it says nothing about authentication, rate limits, error or not-found behavior for a missing LEI, or handling of entities with no parent.

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?

One tightly written sentence that front-loads the operation and where it comes from (live GLEIF v1 API), then lists outputs. No filler, no restating of the title.

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

Completeness3/5

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

An output schema exists and annotations cover safety and openness, so the returned-field enumeration is largely redundant while genuine gaps remain: no guidance on when this beats `lei_check` and no mention of failure modes for invalid or unknown LEIs. Adequate but not complete for a sole-parameter external lookup with a sibling of similar sounding purpose.

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?

There is a single parameter with 100% schema description coverage ("20-character ISO 17442 Legal Entity Identifier"), so the schema already does the explanatory work. The description adds no format hints, example handling, or validation notes beyond that, so the baseline 3 for high-coverage schemas 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?

Names a specific verb and resource: a live GLEIF v1 API lookup of LEI records, and enumerates the data returned (entity status, legal address, LOU registration, parent relationships, digest, receipt). It is clear what the tool does, but it never distinguishes itself from the sibling `lei_check`, so an agent cannot tell the two apart from the definition alone.

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

Usage Guidelines2/5

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

The word "Live" hints at real-time retrieval versus a possibly cached or validation-only sibling, but no explicit when-to-use, when-not-to-use, or alternative is stated. Nothing tells the agent when to pick this over `lei_check` or `counterparty_live_dossier`, leaving routing purely to inference.

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.