Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

by io.github.findimitrov
OverviewDiscussionsAdmin

Map Instrument IDs via OpenFIGI

MapInstrumentIds
Read-onlyIdempotent
    Map financial instrument identifiers between different ID systems using
    Bloomberg's OpenFIGI service. Converts between ticker symbols, ISINs,
    CUSIPs, and FIGIs in a single call.

    Use this tool when:
    - You have a ticker and need the ISIN or CUSIP (or vice versa)
    - You are normalizing instrument IDs when combining data from EDGAR,
      Yahoo Finance, and other sources that use different ID schemes
    - You need to identify what exchange a security trades on

    Supported idType values:
    - 'TICKER': Stock ticker symbol (e.g. 'AAPL')
    - 'ID_ISIN': ISIN (e.g. 'US0378331005')
    - 'ID_CUSIP': CUSIP (e.g. '037833100')
    - 'ID_FIGI': Bloomberg FIGI

    Include 'exchCode': 'US' to target US exchanges for ticker lookups.

    Source: Bloomberg OpenFIGI API. No API key required (optional key raises rate limits).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"New value: +"f258bd16-f060-4e4a-a55d-221a0484866d"
  2. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"d9f77642-e017-4785-9150-e658c2dba3a0"New value: +"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"
  3. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"New value: +"d9f77642-e017-4785-9150-e658c2dba3a0"
  4. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"3775b46a-5aa8-4586-af57-2453c8bcd08c"New value: +"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"
  5. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"d81a5175-11e9-494a-baa5-71d4ffad4ab9"New value: +"3775b46a-5aa8-4586-af57-2453c8bcd08c"
  6. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"9e7f8798-7d22-4378-b93d-179c6f8cb854"New value: +"d81a5175-11e9-494a-baa5-71d4ffad4ab9"
  7. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"9919ff85-e960-472f-863b-3de4c5abed9f"New value: +"9e7f8798-7d22-4378-b93d-179c6f8cb854"
  8. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"38452924-d5df-4668-b51c-d7cd5acabc09"New value: +"9919ff85-e960-472f-863b-3de4c5abed9f"
  9. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"fa72f604-6239-428b-81df-11f07c2c8d00"New value: +"38452924-d5df-4668-b51c-d7cd5acabc09"
  10. Changed1 schema field changed
    • changedInput schema / $defs / OpenFIGIMapParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  11. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful operational context beyond annotations: it names the external OpenFIGI service, states that no API key is required, and notes that an optional key raises rate limits. This is meaningful behavioral disclosure.

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 description is well-structured with a clear opening, bulleted use cases, a supported-values list, and a source note. It is slightly longer than necessary and repeats some schema content, but every section contributes useful guidance and the main purpose is front-loaded.

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?

Given the output schema and annotations, the description covers the core use cases, supported ID types, exchange targeting, and API key/rate-limit context. It relies on the schema for optional mapping fields and generic parameters, which is acceptable, but it does not mention alternative sibling tools or when not to use this tool.

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?

The schema already documents the mappings structure, idType options, and examples, so the description's idType list is partially redundant. The description does add the exchCode 'US' targeting hint and clarifies the no-API-key requirement, but it omits ID_COMMON and ID_WERTPAPIER, which the schema lists as supported values.

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?

The description clearly states a specific verb and resource: 'Map financial instrument identifiers between different ID systems using Bloomberg's OpenFIGI service' and lists the concrete conversions (ticker, ISIN, CUSIP, FIGI). It is clear and specific, though it does not explicitly differentiate itself from sibling tools like SearchFigiInstruments or LookupTicker.

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 provides an explicit 'Use this tool when' section with three concrete scenarios, including normalizing IDs across EDGAR/Yahoo Finance and identifying exchanges. It gives clear context but does not mention exclusions or when a sibling tool would be preferable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fintel Discovery — Financial Intelligence for AI Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources