Skip to main content
Glama

Openfigi Search

openfigi_search
Read-onlyIdempotent

Identify a specific financial instrument by name and get its FIGI — municipal bonds ("munis"), corporate and government bonds, equities, funds and futures. For a municipal bond, pass the issuer as it appears on the bond ("CALIFORNIA ST", "NEW YORK ST DORM AUTH") with marketSecDes "Muni": each result returns a FIGI plus a ticker carrying the coupon and maturity, e.g. "CA CAS 4.5 06/01/2013", which is what identifies one bond among an issuer's many. Answers "which bond is this", "find the FIGI for this issuer's bonds", "what municipal bonds has California issued under this name". Returns identifiers only — no price, no yield, and no reported trade data.

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": {
      "query": "Apple Inc"
    },
    "name": "openfigi_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesInstrument or issuer name as written on the security, e.g. "Apple Inc", "CALIFORNIA ST", "NEW YORK ST DORM AUTH".
currencyNoCurrency filter, e.g. "USD".
exchCodeNoExchange code, e.g. "US". Municipal bonds have no exchange — leave this off for munis.
marketSecDesNoMarket sector. Pass "Muni" to restrict to municipal bonds; other values include "Corp", "Equity", "Govt", "Comdty".
securityTypeNoSecurity type, e.g. "FIXED" for a fixed-rate bond.

Output Schema

NameRequiredDescriptionDefault
dataNo
nextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful negative scope — returns identifiers only, no price, no yield, no trade data — which prevents misuse for valuation questions. It does not address how many matches come back or how to handle ambiguous issuer names, which matters for open-world searches.

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 core purpose is front-loaded in the first clause, and the muni guidance follows immediately. The three quoted example questions are somewhat redundant with each other and with the opening sentence, adding length without much new information.

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, so the description needn't document return fields, and it correctly focuses on the domain nuance (muni issuer names, ticker format) plus the limits of what is returned. For an open-world search that can return many matches, it should say whether results are a list, whether they are capped, and how to disambiguate an issuer with many bonds.

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% and each parameter is already documented with examples, so the baseline applies. The description's parameter content (use marketSecDes "Muni", omit exchCode for munis) largely restates the schema rather than adding new meaning; its real addition is explaining how to read the returned ticker, which is output semantics, not parameter semantics.

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 opens with a specific verb and resource: identify an instrument by name and return its FIGI, and it enumerates the covered asset classes (munis, corporate/government bonds, equities, funds, futures). It stops short of distinguishing itself from the closest sibling, openfigi_map, so an agent cannot tell from this text alone which of the two lookup tools to pick.

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 gives concrete operational guidance for the trickiest case: for a municipal bond, pass the issuer as it appears on the bond with marketSecDes "Muni", and the schema-backed note that munis have no exchange. It also lists the natural-language questions it answers. The gap is that it never states when to use a different tool instead, nor any failure conditions.

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.