Openfigi

Filter

filter

Read-onlyIdempotent

Look up instruments by one exact identifier type and value — idType "TICKER", "ID_ISIN", "ID_CUSIP" or "ID_SEDOL" — and get the matching FIGIs with market sector, including municipal and corporate bonds. Use for an exact-identifier lookup; use search when you only have an issuer or company name. Returns identifiers only, never prices or trades.

Input Schema

Name	Required	Description	Default
`value`	Yes
`idType`	Yes
`currency`	No
`exchCode`	No

Output Schema

Name	Required	Description	Default
`count`	No
`items`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 18, 2026

addedOutput schema / properties / count
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / items

Added value: +{
+  "items": {
+    "properties": {
+      "data": {
+        "items": {
+          "properties": {
+            "compositeFIGI": {
+              "type": "string"
+            },
+            "exchCode": {
+              "type": "string"
+            },
+            "figi": {
+              "type": "string"
+            },
+            "marketSector": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "securityDescription": {
+              "type": "string"
+            },
+            "securityType": {
+              "type": "string"
+            },
+            "securityType2": {
+              "type": "string"
+            },
+            "shareClassFIGI": {
+              "type": "string"
+            },
+            "ticker": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "error": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / query

Removed value: -{
-  "description": "Filter parameters (idType, idValue, exchCode, currency)",
-  "type": "object"
-}

removedOutput schema / properties / result

Removed value: -{
-  "description": "Array of matching instruments",
-  "items": {
-    "description": "Instrument record matching the filter criteria",
-    "type": "object"
-  },
-  "type": "array"
-}

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "exchCode": "UN",
+    "idType": "TICKER",
+    "value": "MSFT"
+  },
+  {
+    "currency": "USD",
+    "idType": "ISIN",
+    "value": "IE00B4L5Y983"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "query": {
+      "description": "Filter parameters (idType, idValue, exchCode, currency)",
+      "type": "object"
+    },
+    "result": {
+      "description": "Array of matching instruments",
+      "items": {
+        "description": "Instrument record matching the filter criteria",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond the annotations: it returns only identifiers (not prices/trades), includes market sector, and covers municipal and corporate bonds. It does not mention pagination or result limits, but for a read-only lookup tool with strong annotation coverage, the description adds meaningful behavioral detail.

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 sentences with no filler. The core purpose and identifier types are front-loaded, the alternative tool is named, and the return scope is stated. Every sentence 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?

The tool has an output schema, so return values are documented elsewhere. The description covers the key decision factors: exact identifier lookup, supported idTypes, what is returned, and what is not returned. It does not explicitly explain the optional `currency` and `exchCode` parameters, but the examples in the schema partially cover that. For a read-only lookup tool with strong annotations and an output schema, this is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden of explaining parameters. The description explains `idType` by listing valid values ('TICKER', 'ID_ISIN', 'ID_CUSUL' or 'ID_SEDOL') and explains `value` as the identifier value. It also implies `currency` and `exchCode` are optional filters via the examples, though it doesn't explicitly describe them. The description compensates for the schema's lack of descriptions, but leaves the optional filter parameters slightly under-explained.

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?

The description states a specific verb ('look up'), a resource ('instruments'), and the exact matching criteria ('one exact identifier type and value'), and it names the identifier types supported. It also distinguishes itself from the sibling `search` tool by explicitly saying what it is not for ('use `search` when you only have an issuer or company name'). This is a clear, specific purpose that an agent can act on without opening the 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?

The description explicitly says when to use this tool ('exact-identifier lookup') and when to use the alternative (`search` for issuer/company name). It also states what the tool returns ('matching FIGIs with market sector') and what it does not return ('never prices or trades'), which helps an agent decide whether this tool is appropriate for the task. This is explicit usage guidance with a named alternative.

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

All Openfigi tools Inspect

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.