Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

by io.github.findimitrov
OverviewDiscussionsAdmin

Search GLEIF for Legal Entity Identifier (LEI)

SearchLEI
Read-onlyIdempotent
    Search the Global Legal Entity Identifier Foundation (GLEIF) database
    for Legal Entity Identifiers (LEIs) by entity name. Returns the 20-character
    LEI code, legal name, registration status, legal address, and jurisdiction.

    Use this tool when:
    - You need the LEI for a financial institution or fund company
    - You want to verify the legal registration of a firm
    - You are cross-referencing SEC EDGAR entities with their global LEI
    - You need to look up parent/subsidiary relationships (use GetLEIDetail)

    LEIs are required for regulatory reporting under MiFID II, EMIR, and Dodd-Frank.
    Cover 2M+ legal entities globally across 200+ jurisdictions.

    Source: GLEIF API (api.gleif.org). No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"f258bd16-f060-4e4a-a55d-221a0484866d"New value: +"05525087-35e9-4aac-b06d-6d88ce386b2e"
  2. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"New value: +"f258bd16-f060-4e4a-a55d-221a0484866d"
  3. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"d9f77642-e017-4785-9150-e658c2dba3a0"New value: +"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"
  4. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"New value: +"d9f77642-e017-4785-9150-e658c2dba3a0"
  5. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"3775b46a-5aa8-4586-af57-2453c8bcd08c"New value: +"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"
  6. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"d81a5175-11e9-494a-baa5-71d4ffad4ab9"New value: +"3775b46a-5aa8-4586-af57-2453c8bcd08c"
  7. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"9e7f8798-7d22-4378-b93d-179c6f8cb854"New value: +"d81a5175-11e9-494a-baa5-71d4ffad4ab9"
  8. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"9919ff85-e960-472f-863b-3de4c5abed9f"New value: +"9e7f8798-7d22-4378-b93d-179c6f8cb854"
  9. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"38452924-d5df-4668-b51c-d7cd5acabc09"New value: +"9919ff85-e960-472f-863b-3de4c5abed9f"
  10. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"fa72f604-6239-428b-81df-11f07c2c8d00"New value: +"38452924-d5df-4668-b51c-d7cd5acabc09"
  11. Changed1 schema field changed
    • changedInput schema / $defs / LEISearchParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  12. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds source (GLEIF API), no API key required, coverage size, and regulatory context, but omits search fuzziness, pagination, rate limits, or result-ordering behavior. With annotations covering safety, this is adequate but not rich.

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?

Well-structured and front-loaded, with the core purpose first and bulleted usage guidance. The regulatory and coverage sentences add context but are slightly marketing-oriented for a simple search tool.

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 annotations covering safety and an output schema covering return values, the description supplies usage, source, and domain context. It omits filter and limit behavior, but the input schema covers those, so it is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description only mentions searching by entity name and lists return fields. Other schema parameters such as limit, country, wholesaler_ids, and source_resource_id are not addressed, and the reported schema description coverage is 0%, so the description fails to compensate for input semantics.

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 ('Search') and resource ('GLEIF database for LEIs by entity name'), and lists return fields. It explicitly distinguishes itself from GetLEIDetail for parent/subsidiary lookups, helping route between siblings.

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

Usage Guidelines5/5

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

Provides explicit 'Use this tool when' bullets covering LEI lookup, registration verification, EDGAR cross-referencing, and notes the alternative GetLEIDetail for relationship queries. Clear when-to-use context and a named alternative.

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

All Fintel Discovery — Financial Intelligence for AI Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources