Skip to main content
Glama

Openfigi Map

openfigi_map
Read-onlyIdempotent

Convert identifiers you already hold into FIGIs, in bulk — ISIN, CUSIP, SEDOL, ticker or CIK to the Financial Instrument Global Identifier, for bonds (municipal and corporate), equities and funds. Use when you have a list of identifiers and need the common key to join them on; use search instead when you only have a name. Passing a CUSIP you already possess as a lookup input is fine — the response is keyed on FIGI.

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": {
      "jobs": [
        {
          "idType": "TICKER",
          "idValue": "AAPL",
          "exchCode": "UN"
        },
        {
          "idType": "ISIN",
          "idValue": "US0378331005",
          "securityType": "Common Stock"
        }
      ]
    },
    "name": "openfigi_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobsYesEach job: {idType, idValue, exchCode?, securityType?, marketSecDes?, currency?}. idType is e.g. "ID_ISIN", "ID_CUSIP", "ID_SEDOL", "TICKER". For municipal bonds set marketSecDes: "Muni".

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesArray of mapping results for each job

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the description rightly focuses elsewhere: it discloses batching ('in bulk') and that the response is keyed on FIGI, plus a licensing-adjacent reassurance that supplying a CUSIP as input is acceptable. What it omits is operationally material for a proxy API: no mention of per-request job caps or rate limits, which are a real constraint on a bulk conversion tool.

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?

Three sentences, front-loaded with the conversion and scope, then the routing rule, then the CUSIP caveat. No filler, though the closing CUSIP sentence is the least essential of the three and reads as a defensive note rather than core guidance.

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?

An output schema exists and annotations cover the safety profile, so the description does not need to explain return values, and it correctly spends its space on scope and routing. The remaining gap is operational: for a batch tool against an open-world API, the absence of any job-count or rate-limit guidance leaves an agent unable to size its calls safely.

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%, so the nested `jobs` shape and optional fields are already documented, and the baseline is 3. The description adds asset-class framing and mentions CIK, which the schema's example idType list does not, but it also names bare forms ('ISIN', 'CUSIP') while the schema expects prefixed values ('ID_ISIN', 'ID_CUSIP'), which mildly muddies rather than sharpens parameter meaning.

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 ('Convert identifiers ... into FIGIs, in bulk'), enumerates the accepted input identifier types (ISIN, CUSIP, SEDOL, ticker, CIK) and the covered asset classes (muni/corporate bonds, equities, funds). It also explicitly contrasts itself with the `openfigi_search` sibling, so an agent can route 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 Guidelines5/5

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

Gives a positive trigger ('when you have a list of identifiers and need the common key to join them on') and a negative one with a named alternative ('use `search` instead when you only have a name'). The when/when-not pair is explicit rather than inferred.

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.