Skip to main content
Glama
SEC EDGAR, UK Companies House & LEI MCP Server

SEC EDGAR, UK Companies House & LEI MCP Server

by willowswt

trace_global_corporate_ownership_lei

Read-onlyIdempotent

Trace global corporate ownership by searching the GLEIF LEI Registry with a legal entity name or 20-character LEI, returning entity details and direct/ultimate parent links across 200+ jurisdictions.

Instructions

Search the official GLEIF Global Legal Entity Identifier (LEI) Registry (api.gleif.org) by legal entity name or 20-character LEI (query) across 200+ jurisdictions, returning LEI, legal name, jurisdiction, registration ID, headquarters address, entity status, and direct/ultimate parent ownership links.

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": "trace_global_corporate_ownership_lei"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCompany legal name or 20-char LEI code (e.g. 'Stripe', 'Revolut', 'ASML').
maxResultsNoMaximum entities to return (1-15, default 6).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive, so the safety profile is covered; the description adds real value by identifying the authoritative upstream source (api.gleif.org), the jurisdictional breadth, and enumerating what the response contains, including direct/ultimate parent ownership links. It does not mention rate limits, auth requirements, or how many hops of ownership linkage are resolved, which keeps it off 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?

One dense but front-loaded sentence: the verb, registry, and query form come first, followed by returns. Every clause carries information; the return-field enumeration is slightly list-heavy but justified given no output schema exists.

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 correctly spends its space enumerating returned fields, and both input parameters are documented via the schema. The main remaining gap is any statement of how ownership links are resolved or what happens when no match exists, but for a two-parameter read-only lookup this is close to complete.

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% and both parameters are fully described there, so baseline is 3. The description restates the query semantics (legal name or 20-character LEI) but adds nothing new, and maxResults is not mentioned at all in the description.

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?

Names a specific verb+resource ('Search the official GLEIF LEI Registry') plus the lookup key and the returned fields, so an agent can tell this is a global LEI/entity-ownership lookup rather than a filings or financials search. Sibling differentiation is only implicit via the registry name ('GLEIF LEI' vs SEC EDGAR/Companies House), never stated explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the scope phrase 'across 200+ jurisdictions' and 'official' source, which hints at when this is preferable to national registries, but there is no explicit when-to-use/when-not or named alternative among the sibling tools. The agent must infer the routing decision.

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