Skip to main content
Glama
Bosco Labs Data

Bosco Labs Data

Official

LEI lookup (GLEIF, free)

get_lei_record
Read-only

Retrieve official GLEIF Legal Entity Identifier records to identify a company by LEI or name, confirming its legal name, status, jurisdiction, local registration number and ultimate parent.

Instructions

Free, no API token needed. Legal Entity Identifier (LEI) lookup in the official GLEIF register: about 2.9 million companies, funds and other legal entities worldwide (source: GLEIF API, CC0 open data). Use it to identify a company: its exact legal name, LEI, whether it is active, its jurisdiction and country, its local registration number and its ultimate parent company.

Pass an LEI (exact record) or a company name (best matches first; check `legal_name`).

Returns one row per entity: lei, legal_name, entity_status (ACTIVE/INACTIVE),
registration_status (ISSUED, LAPSED, ...), jurisdiction, legal_address_country,
legal_address_city, headquarters_country, registered_as (local registry number),
ultimate_parent (lei, legal_name; when reported), source_url (the GLEIF record; cite it)
and next_steps (the paid Bosco Labs call for this company's financials: tool and
arguments on the remote MCP server and HTTP API, stdio_tool in this package).

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": {
      "query": "<query>"
    },
    "name": "get_lei_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA 20-character LEI, e.g. 724500Y6DUVHQD6OXN27, or a company name, e.g. "Heineken"
max_resultsNoMax companies for a name search (1-5).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the read-only and open-world annotations, it discloses that the tool is free, needs no API token, uses the official GLEIF register, covers about 2.9 million entities, returns one row per entity, and includes a source URL to cite. It does not discuss rate limits or pagination behavior, but it adds substantial context for a lookup tool.

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?

The description is front-loaded with the key access fact, purpose, and query modes, then summarizes returned fields. It is somewhat long and enumerates return fields despite the presence of an output schema, but the structure remains clear and most sentences carry useful context.

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

Completeness5/5

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

Given the low-complexity lookup shape, existing output schema, and annotations, the definition is complete enough for correct invocation. It explains access requirements, data source, query modes, result scope, key returned concepts, citation guidance, and a next-step route to financial data.

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%, and the description adds useful semantics for `query`: an LEI produces an exact record, while a company name returns best matches first and callers should check `legal_name`. It does not explain `max_results`, but the schema already documents that parameter fully.

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 a specific verb and resource: an LEI lookup in the official GLEIF register, returning identity data such as legal name, status, jurisdiction, and ultimate parent. It is clear what the tool does, but it does not explicitly contrast itself with sibling tools such as company accounts, annual reports, or SEC filings.

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 guidance: use it to identify a company, pass an exact LEI for a single record, or pass a company name for best-match search results and check `legal_name`. It does not provide explicit when-not-to-use guidance or name alternative tools for overlapping needs.

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