Skip to main content
Glama

UK company & compliance data

Global LEI Register: LEI by ISIN

gleif__by-isin
Read-onlyIdempotent

Which entity issued a security, by ISIN. 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": {
      "isin": "<isin>"
    },
    "name": "gleif__by-isin"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinYesISIN

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 cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), and the description adds genuinely new operational context: a free daily allowance followed by $0.003 USDC per call via x402. That cost/quota disclosure is exactly the kind of behavioral detail annotations cannot express, though auth/payment setup mechanics remain unstated.

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 short sentences, zero padding, with the core purpose front-loaded before the pricing note. Every clause earns its place.

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 an output schema present, return values need not be explained, and the pricing/allowance note covers a key operational concern. The only real gap is routing relative to the closely-named gleif__isins sibling, which is not addressed.

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?

Only one parameter (isin) at 100% schema coverage, so the schema already carries the burden and baseline 3 applies. The description adds no format guidance (e.g. that ISIN is a 12-character alphanumeric code) beyond what the schema's 'ISIN' label provides.

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?

States a specific resolution: ISIN -> issuing entity (LEI), which is a clear verb+resource pairing an agent can act on. It does not, however, distinguish itself from the sibling gleif__isins tool, which an agent could easily confuse with this one.

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?

The description gives pricing context but no when-to-use guidance: nothing says whether to reach for gleif__by-isin versus gleif__isins or gleif__search, and no prerequisites (e.g. valid ISIN required) are stated. Usage is only implied by the one-line purpose.

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