NewKwLab Tools

verify_lei

Verify a Legal Entity Identifier (LEI, ISO 17442) against the GLEIF registry: legal name, entity status, registration status and next renewal date, with a plain-language flag when the record has lapsed or has other issues.

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

Input Schema

Name	Required	Description	Default
`lei`	Yes	20-character LEI code

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It helpfully discloses the returned fields and a notable behavior — a plain-language flag when the record has lapsed — but is silent on what happens for an invalid-format or not-found LEI, and whether the lookup is live or cached.

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?

A single front-loaded sentence leading with the action and resource, with no wasted framing. The trailing enumeration of checked fields is slightly dense but each item is informative.

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?

For a simple one-parameter lookup with no annotations and no output schema, the description covers the identity of the resource, the data source, the return content, and the lapse flag. The main remaining gap is error/not-found behavior, which is modest for a low-risk read operation.

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?

With a single parameter at 100% schema coverage, the schema already documents the 20-character LEI code. The description corroborates it via the ISO 17442 reference but adds no syntax, normalization, or case-handling guidance beyond what the schema supplies.

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 (Verify) plus the exact resource (LEI, ISO 17442), the authority it checks against (GLEIF registry), and the fields returned. An agent can distinguish this from search_lei_by_name on the strength of 'verify a given code' vs. 'search by name' 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 Guidelines3/5

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

Usage is implied by the required 20-character LEI input: this is the tool to call when you already hold a code rather than a name. However, it never explicitly names search_lei_by_name as the alternative when only a name is known, and gives no exclusions or preconditions (e.g., malformed codes).

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

All NewKwLab Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?