Skip to main content
Glama

Gleif Group Members

gleif_group_members
Read-onlyIdempotent

Every entity in a corporate group, across all jurisdictions, in ONE call, built on the GLEIF golden copy (every Level 2 relationship record). Give any member of the group (LEI or company name): the tool climbs to the group's ultimate accounting-consolidation parent and returns every entity that reports it as ultimate parent, every descendant over direct-parent links, and the international branches of any of them. Aggregates are over the WHOLE group (member_count, jurisdiction_count, by_jurisdiction); the member list is capped by limit and says so. Each member carries depth below the root, direct_parent_lei, consolidation % where reported, jurisdiction and LEI status. Answers "all subsidiaries of Siemens worldwide", "which countries does this group have legal entities in", "who is the ultimate parent of this company and what else does it own". Use this over lei_hierarchy_tree for large groups (that tool walks one node at a time and truncates at 150). Fund-management links (IS_FUND-MANAGED_BY / IS_SUBFUND_OF) are NOT ownership and are not included. Response carries data_as_of (the GLEIF publish time the answer reflects).

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": "Siemens"
    },
    "name": "gleif_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYesA 20-character LEI of ANY group member, e.g. "W38RGI023J3WT1HWRP32" (Siemens AG), OR a company name, e.g. "Siemens", resolved against the GLEIF entity register (a subsidiary match still lands on the whole group). Do not construct an LEI.
limitNoMax members to list, 1-2000 (default 300). Counts and by_jurisdiction always cover the whole group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lei / description
      Previous value: -"A 20-character LEI of ANY group member, e.g. \"W38RGI023J3WT1HWRP32\" (Siemens AG), OR a company name, e.g. \"Siemens\" — resolved against the GLEIF entity register (a subsidiary match still lands on the whole group). Do not construct an LEI."New value: +"A 20-character LEI of ANY group member, e.g. \"W38RGI023J3WT1HWRP32\" (Siemens AG), OR a company name, e.g. \"Siemens\", resolved against the GLEIF entity register (a subsidiary match still lands on the whole group). Do not construct an LEI."
  2. Added

TDQS

A4.4/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 open-world, so the safety profile is covered. The description adds real behavioral context beyond that: it climbs to the ultimate accounting-consolidation parent, aggregates cover the whole group while the member list is capped by limit, and the response carries data_as_of. It does not describe error behavior when a name is ambiguous or unmatched, which keeps it below the top band.

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-loaded with the core promise and the sibling comparison early, and every sentence carries information (scope, aggregation semantics, exclusions, freshness). It is a dense single paragraph, though, and the example-question list is slightly padded.

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?

No output schema exists, so the description must carry return-value semantics, and it does: member fields (depth, direct_parent_lei, consolidation %, jurisdiction, LEI status), aggregate fields, truncation signaling, and data_as_of. For a two-parameter read tool this is complete enough to call correctly.

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%, so the baseline is 3, but the description adds meaning: any group member (LEI or name) resolves to the whole group, and the limit caps only the member list while counts and by_jurisdiction always cover the full group. That clarifies the interaction between the two parameters in a way the schema alone does not.

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 ('returns every entity in a corporate group') with explicit scope ('across all jurisdictions, in ONE call') and names the sibling it supersedes (lei_hierarchy_tree). An agent can distinguish it from the hierarchy-tree tool without opening either 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 explicit when-to-use routing ('Use this over lei_hierarchy_tree for large groups... truncates at 150'), concrete example questions it answers, and an explicit exclusion (fund-management links are not ownership and are not included). Both the positive and negative selection conditions are stated.

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.