Skip to main content
Glama

Isin To Lei

isin_to_lei
Read-onlyIdempotent

Resolve an ISIN (12-character international securities identifier, e.g. "CH0038863350" or "DE0007164600") to the LEGAL ENTITY that issued the security: its LEI, registered legal name, jurisdiction, and status, via the official GLEIF ISIN-to-LEI mapping. Answers "who issued this security" / "which company is behind ISIN X" for non-US as well as US securities. An ISIN identifies one security while the issuer typically has many, the response says what it resolved TO. A valid ISIN with no mapping yet is reported as unmapped (the mapping lags new issuance), distinct from an invalid ISIN.

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": {
      "isin": "DE0007164600"
    },
    "name": "isin_to_lei"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinYes12-character ISIN, e.g. "CH0038863350" (2-letter country prefix + 9-char NSIN + check digit)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With annotations already declaring readOnly, idempotent, openWorld, and non-destructive, the description adds real value beyond them: it names the authoritative data source (official GLEIF ISIN-to-LEI mapping) and distinguishes three outcome states — resolved, unmapped, and invalid — including the caveat that mapping lags new issuance. It does not mention rate limits, caching, or auth needs, which keeps it just below the top mark.

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 with the verb and the mapping direction, then layers in return fields and edge cases, so the important information comes first. It is somewhat dense and repeats ISIN examples already present in the schema, which is minor waste but not harmful.

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 takes on the burden of describing what comes back (LEI, legal name, jurisdiction, status) and how to interpret an empty result (unmapped vs invalid). That is nearly sufficient for a one-parameter read tool; only resolution/caching or confidence details are absent, and those are optional here.

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 parameter, and the schema already documents the 12-character format, the country-prefix/NSIN/check-digit structure, and examples. The description mainly restates that format with its own examples, adding no new syntactic or constraint detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and directional mapping (ISIN -> LEI) plus the exact return fields (LEI, registered legal name, jurisdiction, status). It explicitly frames the direction of resolution ('An ISIN identifies one security while the issuer typically has many'), which distinguishes it from a reverse-direction sibling such as lei_to_isins without needing to name it.

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?

It states the user-intent phrasings that select this tool ('who issued this security' / 'which company is behind ISIN X') and notes coverage for non-US as well as US securities, which is clear usage context. It stops short of naming an alternative tool or spelling out exclusions (e.g., when to use get_lei instead for direct entity lookup by name or LEI).

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.