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

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Filter parameters (idType, idValue, exchCode, currency)
`result`	No	Array of matching instruments

Schema Changelog

Changes observed during successful MCP inspections.

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds meaningful context beyond those hints: exact-match semantics, inclusion of municipal and corporate bonds, and the hard boundary that it returns identifiers but never prices or trades. No contradiction with the annotations.

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 wasted words: the first states scope and output, the second gives usage routing, and the third sets a clear return boundary. The most important information 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?

For a read-only identifier lookup, the description plus annotations and output schema cover the core calling context: exact idType/value, what is returned, and what is never returned. The main gap is the absence of semantics for the optional filter parameters, which keeps it just short of fully complete.

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 description compensates for 0% schema coverage by documenting the allowed idType values ('TICKER', 'ID_ISIN', 'ID_CUSIP', 'ID_SEDOL') and emphasizing exact value matching for the two required parameters. However, the optional parameters `currency` and `exchCode` are not explained in the description, so an agent must infer their meaning solely from schema examples.

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: 'Look up instruments by one exact identifier type and value' and names the output, 'matching FIGIs with market sector.' It also explicitly contrasts with `search`, giving an agent an immediate way to distinguish the two tools without opening their schemas.

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?

Explicitly says to use this tool for an exact-identifier lookup and tells the agent to use `search` when only an issuer or company name is available. The return boundary — identifiers only, never prices or trades — also helps prevent misuse.

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.