Skip to main content
Glama

Lei Hierarchy Tree

lei_hierarchy_tree
Read-onlyIdempotent

Walk the FULL corporate ownership hierarchy for an entity in one call: the ancestor chain from the entity up to its ultimate parent, plus a multi-level tree of subsidiaries below it (breadth-first over GLEIF Level 2 direct-child records, depth-limited, depth stated in the response). Accepts a 20-character LEI or a company NAME. Answers "everything this group ultimately controls" / "full subsidiary tree of Deutsche Bank" / "who is at the top of this entity's ownership chain", use get_lei_relationships instead when one hop (direct parent + direct children) is enough.

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": "INR2EJN1ERAN0W5ZP974",
      "depth": 2
    },
    "name": "lei_hierarchy_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYes20-character LEI code OR a company name (resolved automatically, match echoed back).
depthNoHow many generations of subsidiaries to descend: 1-4, default 2. The ancestor chain upward is always walked to the top regardless.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuine non-obvious behavior: traversal is breadth-first over GLEIF Level 2 direct-child records, depth-limited, with the depth reported in the response, and the upward chain always runs to the top regardless of the depth parameter. It does not mention cost, latency, or what an unresolved company name produces, which keeps it from a 5.

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?

Front-loads the scope and output shape before the alternative and examples, and every sentence carries information. The second and third sentences are dense enough that they read as a run-on, but little could be cut without losing guidance.

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 no output schema, the description does the work of explaining what comes back: ancestor chain plus a multi-level tree with the applied depth. For a two-parameter read-only tool that is close to sufficient; it leaves unaddressed what happens when a NAME resolves ambiguously or fails, which is the main remaining gap.

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%, so both parameters are already documented, including the 1-4 range and default of depth and the LEI-or-name dual input. The description restates the same facts ('20-character LEI or a company NAME', 'depth stated in the response') without adding new semantics or edge-case behavior, so the baseline 3 applies.

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 and resource ('Walk the FULL corporate ownership hierarchy for an entity'), then enumerates both output components: the ancestor chain to ultimate parent and a multi-level subsidiary tree. It explicitly contrasts itself with get_lei_relationships, so an agent can distinguish the two without opening a schema.

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?

Gives concrete triggering questions ('full subsidiary tree of Deutsche Bank', 'who is at the top of this entity's ownership chain') and an explicit exclusion with the alternative named: use get_lei_relationships when one hop (direct parent + direct children) is enough. This is textbook when/when-not/alternative 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.