Skip to main content
Glama

AgentSupply

Look up legal entity (GLEIF LEI)

lookup_lei
Read-only

Look up a legal entity in the global GLEIF LEI index by 20-character LEI or by company name. Returns legal name, status, jurisdiction and registered address (up to 5 matches for name search). Live tool – free during the pilot, rate-limited.

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

Input Schema

NameRequiredDescriptionDefault
leiNo20-character Legal Entity Identifier.
nameNoCompany name to search for (used when lei is not given).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, open-world lookup. The description adds useful behavioral detail beyond that: returned fields, the 5-match cap for name searches, live operation, free pilot pricing, and rate limiting. It does not cover authentication, error behavior, or pagination, so it is strong but not exhaustive.

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 tightly written sentences front-load the lookup mechanism, then add return fields and operational constraints. Every sentence contributes useful information without repetition.

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?

For a simple two-parameter read-only lookup with no output schema, the description is nearly complete: it covers lookup modes, returned data, match limits, and rate-limit context. The main residual gap is the behavior when neither optional parameter is supplied.

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%, and the schema already documents that lei is a 20-character identifier and name is used when lei is absent. The description reinforces the precedence and adds the name-search match cap, but most parameter meaning is already supplied by the schema.

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 states a specific verb and resource: look up a legal entity in the GLEIF LEI index. It names both accepted lookup keys (20-character LEI or company name), making the tool clearly distinguishable from sibling tools such as check_eu_vat or check_email_domain.

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 usage context: use the LEI for direct lookup, or a company name when the LEI is not given, with up to 5 name matches. It does not explicitly state when to prefer this tool over alternatives or what happens when neither input is supplied, so it falls short of full when/when-not guidance.

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