Skip to main content
Glama
eu-kyb-mcp

eu-kyb-mcp

by mastermabel

Look up legal entity (GLEIF LEI)

lookup_lei
Read-only

Retrieve up to five legal entity matches from the GLEIF LEI index by 20-character LEI or company name, with exact name matches first, to verify status, jurisdiction, and registered address.

Instructions

Look up a legal entity in the global GLEIF LEI index by 20-character LEI or by company name. Returns legal name, status, jurisdiction and registered address (up to 5 matches, exact name matches first).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_lei"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNo20-character Legal Entity Identifier
nameNoCompany name (used when lei is not given)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, and the description adds real value by disclosing the returned fields, the 5-match cap, and the exact-match-first ordering. It omits auth/rate-limit characteristics and what happens on zero matches, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler; the input modes come first and the return behaviour second. Every clause carries information an agent needs.

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 compensates by enumerating the returned fields and the match cap, and the read-only/open-world nature is covered by annotations. The gap is that with zero required parameters it never states that one of lei or name must be supplied, nor what both/neither produce.

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, and the description largely repeats that (20-character LEI, name used when lei absent). It does add one useful semantic detail — that name lookups can return up to 5 fuzzy matches with exact matches ranked first — but that pertains to results rather than to the parameters themselves.

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 (look up) and resource (legal entity in the GLEIF LEI index), plus the two accepted lookup keys. The resource is clearly distinct from the sibling tools (email domain, EU VAT, verification report), so an agent can select it without opening the schema.

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?

The description implies the two usage modes (by LEI or by company name) and notes name is the fallback path, but it gives no explicit when-to-use/when-not-to-use guidance and never names an alternative tool or a prerequisite. Guidance is inferable rather than stated.

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