Skip to main content
Glama

UK company & compliance data

Global LEI Register: Direct children

gleif__direct-children
Read-onlyIdempotent

Entities directly owned by this entity. Free within the daily allowance, then $0.003 USDC per call via x402.

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": {
      "lei": "<lei>"
    },
    "name": "gleif__direct-children"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYesLEI

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real information beyond that: the call is free within a daily allowance and then billed at $0.003 USDC per call via x402, which is exactly the kind of metering detail a caller needs before invoking.

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?

Two sentences, zero filler: the purpose lead is front-loaded and the pricing caveat follows it. Nothing is repeated from the title or the schema, and every clause carries information.

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?

An output schema exists, so the description need not explain return values, and the annotations cover the safety profile. Purpose plus cost model plus those structured fields give an agent what it needs, with only the hierarchy-depth semantics of 'direct' being left implicit.

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 description coverage is 100% for the single 'lei' parameter, so the schema already carries the parameter documentation and the baseline of 3 applies. The description adds no format, validation, or sourcing detail about the LEI argument, so nothing pushes it above baseline.

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?

The description names a specific resource ('entities directly owned by this entity'), which is enough for an agent to understand the tool returns the ownership subtree one level below the given LEI. It stops short of explicitly contrasting itself with the semantically adjacent siblings (gleif__direct-parent, gleif__ultimate-parent, gleif__branches), so the 'direct' vs 'ultimate' distinction is left to inference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only usage-relevant signal is the commercial framing, which tells the agent a call is free up to a daily allowance and then metered, but that is cost context rather than selection 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.

Resources