Skip to main content
Glama

Lei To Isins

lei_to_isins
Read-onlyIdempotent

List ALL ISINs (securities) issued by a legal entity, from the official GLEIF ISIN-to-LEI mapping. Accepts a 20-character LEI or a company NAME (resolved automatically and echoed back). Answers "what securities has this company issued" / "all ISINs for Nestlé". Returns the full set, bonds, share lines, ADRs, not a single value; an entity that exists but has no mapped ISINs returns an empty set with that stated.

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": "KY37LUS27QQX7BB93L28"
    },
    "name": "lei_to_isins"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYes20-character LEI code (e.g. "KY37LUS27QQX7BB93L28") OR a company name (e.g. "Nestlé"), names are resolved via the LEI registry first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lei / description
      Previous value: -"20-character LEI code (e.g. \"KY37LUS27QQX7BB93L28\") OR a company name (e.g. \"Nestlé\") — names are resolved via the LEI registry first."New value: +"20-character LEI code (e.g. \"KY37LUS27QQX7BB93L28\") OR a company name (e.g. \"Nestlé\"), names are resolved via the LEI registry first."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds useful behavioral context beyond that: company names are resolved automatically and echoed back, the full set is returned rather than a single value, and an entity with no mapped ISINs produces an explicit empty set.

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?

The definition is front-loaded and avoids wasted introductory text. It is a single dense passage with parentheticals, but each piece of information—source, input flexibility, output shape, and empty-result behavior—earns its place.

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?

For a one-parameter lookup with no output schema, the description covers what the agent needs: accepted input forms, automatic name resolution, the full-set return shape including bonds, share lines and ADRs, and the empty-set edge case. Nothing material is left unspecified.

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 the schema already explains that the single parameter accepts a 20-character LEI or a company name resolved via the LEI registry. The description largely repeats that information, adding only the echo-back behavior, so the baseline 3 is appropriate.

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?

The description opens with a specific verb and resource, 'List ALL ISINs (securities) issued by a legal entity,' and names the data source, GLEIF ISIN-to-LEI mapping. This makes the direction of the lookup unmistakable against siblings such as isin_to_lei.

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

Usage Guidelines4/5

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

The description gives clear usage context with example questions like 'what securities has this company issued' and 'all ISINs for Nestlé.' It does not explicitly name alternatives or state when not to use the tool, which keeps it just short of a 5.

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.