Skip to main content
Glama

Check a security by ISIN, CUSIP or ticker

securities_id
Read-only

A security by ISIN, CUSIP or ticker (with an optional exchange code): its OpenFIGI id, name, ticker, exchange, security type and market sector, and for an ISIN the issuer's LEI and legal name from GLEIF. ISIN and CUSIP check digits are verified before the call. Attribution: FIGI by OpenFIGI; LEI by GLEIF. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "securities_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinNoISIN, 12 characters
cusipNoCUSIP, 9 characters
tickerNoTicker, e.g. AAPL
exchangeNoOptional OpenFIGI exchange code, e.g. US or LN

Output Schema

NameRequiredDescriptionDefault
queryNo
issuerNo
sourceNo
checkedAtNo
disclaimerNo
securitiesNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses behavior an agent cannot get elsewhere: ISIN/CUSIP check-digit validation happens before the call, data provenance (OpenFIGI for FIGI, GLEIF for LEI), and a paid model at $0.002 per successful call via x402 with failed calls free. Cost and payment/auth requirements are exactly the kind of operational context annotations do not carry.

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 purpose and accepted identifiers are front-loaded, then output fields, then validation, attribution and pricing — a logical order with no filler sentences. It runs long as a single dense block, but each clause (validation, attribution, cost) carries information an agent needs.

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?

With an output schema present, return values need not be explained, yet the description still summarizes them usefully and fully covers cost, provenance and pre-call validation. The one meaningful omission is that all four parameters are optional (required: 0) and the description never states that at least one identifier must be supplied or how conflicts between identifiers are resolved.

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 coverage is 100%, so baseline is 3; the description goes slightly beyond by noting exchange is optional and by adding a validation rule for isin/cusip (check digits verified) and clarifying that LEI and legal name are returned only for ISIN lookups. It does not say which identifier combinations are valid or what happens if several are supplied.

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 names the resource (a security) and the exact identifiers accepted (ISIN, CUSIP, ticker plus optional exchange code), and enumerates the returned fields (OpenFIGI id, name, ticker, exchange, security type, market sector, LEI/legal name for ISINs). It is a clear lookup definition, but it never distinguishes itself from sibling tools such as lei or company_ticker, so an agent must infer which entry point to use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description tells you which identifier forms are valid and that exchange is optional, but gives no explicit when-to-use / when-not-to-use guidance and no routing to alternatives for LEI-only or ticker-only lookups. The agent can call it correctly, but must reason about selection itself.

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.

Resources