Skip to main content
Glama

Find Instruments

find_instrument
Read-onlyIdempotent

Resolve financial instruments by ticker or ISIN to get detailed card data including type, board, lot size, issuer, and bond/stock specifics. Returns a merged card per instrument by default.

Instructions

Instrument cards by tickers (batch) or ISINs: name, type, boards (classCode/exchange — classCode is needed by candles/orders), lot size, ISIN, issuer; for bonds — face value, maturity, coupon rate/frequency, accrued interest; for stocks — dividend yield, sector, EPS growth, credit rating, BCS score. Start here to resolve a ticker before other calls. By default one merged card per instrument is returned (primary board; other listings in otherBoards; off-exchange rows flagged offExchange) — pass allBoards=true for the raw per-board cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isinsNoISINs (alternative to tickers)
tickersNoTickers, e.g. ["SBER", "LKOH"]
allBoardsNoReturn every per-board card instead of one merged card per instrument
outputPathNoWrite the full result to this file (path relative to the output root: BCS_OUTPUT_DIR or server cwd) instead of returning it inline. The response becomes a short summary {savedTo, records, bytes, sample}. Use for bulk data to keep the context clean. For get_candles this also enables full-history fetching (chunking beyond the 1000-bar API limit).
outputFormatNoFile format; default json (or csv if outputPath ends with .csv). csv writes the main flat array of the response.
Behavior5/5

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

Annotations already declare safe read-only, idempotent, and open-world hints. The description adds valuable context beyond: default merged card behavior, allBoards option, and structure details (primary board, otherBoards, offExchange flag). No contradictions.

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?

The description is compact yet information-dense, front-loading the core purpose and proceeding logically through input, output details, and special cases. No redundant sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple input methods, instrument types, board logic, and no output schema), the description covers all essential aspects: how to use, what is returned per instrument type, board structure, and the allBoards option.

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 coverage is 100% with descriptions for all 5 parameters. The description summarizes input (tickers/ISINs) and output fields but does not add significant meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool finds instrument cards by tickers or ISINs, listing extended fields. It distinguishes itself from siblings by stating 'Start here to resolve a ticker before other calls,' making its role as an entry point explicit.

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 explicit guidance to use this tool first to resolve tickers before other calls. While it doesn't contrast with alternatives like get_instruments_by_type, it establishes a clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/human-turn/bcs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server