Skip to main content
Glama

Kobo Terminal NGX

ISIN and FIGI security master

lookup_identifiers
Read-onlyIdempotent

Maps every NGX ticker to its ISIN and FIGI. 152 securities, 147 with a verified ISIN. Resolve an ISIN or FIGI back to a ticker. Plan: Starter+.

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_identifiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
figiNoResolve a FIGI to its security
isinNoResolve an ISIN to its security. Example: NGDANGCEM008
limitNoRows per page, default 200, max 500
offsetNoPagination offset
identified_onlyNoOnly securities with at least one identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description only needs to add context. It does: coverage figures (152 securities, 147 with verified ISINs) tell the agent to expect partial ISIN coverage, and the 'Starter+' note discloses a plan gate not visible in annotations. It stops short of saying what an unmatched ISIN or FIGI returns.

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?

Three short sentences, front-loaded with the primary ticker-to-identifier direction before the reverse case. The coverage counts and plan tier earn their space by setting expectations; nothing is redundant.

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 all five parameters optional, full schema coverage, and no output schema, the description supplies enough to call the tool correctly: mapping directions, dataset size, partial ISIN coverage, and plan requirement. Only the behavior when both identifier params are passed is left unaddressed.

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%, including an example ISIN value, so the parameters are already fully documented. The description adds only the general resolution framing, nothing about precedence when both figi and isin are supplied, which is the one ambiguity the schema leaves open.

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 and resource with both directions spelled out: 'Maps every NGX ticker to its ISIN and FIGI' and 'Resolve an ISIN or FIGI back to a ticker.' No sibling tool in the catalog performs identifier resolution, so the agent can select it unambiguously.

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 bidirectional mapping sentences convey the triggering condition (you hold a ticker, ISIN, or FIGI and need another form), and 'Plan: Starter+' flags an access prerequisite. There is no explicit when-not or named alternative, but no plausible alternative exists among the siblings.

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