Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

by io.github.findimitrov
OverviewDiscussionsAdmin

Get GLEIF LEI Detail

GetLEIDetail
Read-onlyIdempotent
    Retrieve the full GLEIF LEI record for one legal entity using its
    20-character LEI code. Returns legal name, registration status, legal
    address, headquarters address, managing LOU, and renewal dates.

    Use this tool when:
    - You have a LEI (from SearchLEI) and need full entity details
    - You want to verify the registration status and renewal date
    - You need the exact legal address and jurisdiction of an entity

    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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / 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 / LEIDetailParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  12. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so safety is covered. The description adds useful behavioral context beyond annotations: the source is the GLEIF API, no API key is required, and the response includes legal name, status, addresses, LOU, and renewal dates.

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?

The description is front-loaded with purpose, then a return-field summary, then clear usage bullets, then source details. Every section is brief and useful for selecting and invoking the tool, with no filler.

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 single-entity lookup with rich annotations and an output schema, the description provides enough context to call the tool correctly. It covers source, usage, and the LEI parameter, though it omits edge cases such as invalid or missing LEI handling.

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 description coverage is reported as 0%, so the description must compensate. It specifies that the key input is a 20-character LEI code and directs the agent to obtain it from SearchLEI, which is sufficient for the primary lookup parameter, though it does not explain the optional wrapper/filter fields in 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: retrieve the full GLEIF LEI record for one legal entity using a 20-character LEI code. It also distinguishes the tool from SearchLEI by noting that a LEI is already required and that SearchLEI is the source for obtaining one.

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?

The description gives concrete usage triggers in a bullet list: having a LEI from SearchLEI, verifying registration status, and needing legal address or jurisdiction. It does not explicitly state when not to use the tool or name a direct alternative for full detail, but the context is clear.

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