Finance Database

indices

Read-onlyIdempotent

List market indices matching filters such as category group, category, currency and exchange, or matching a free-text query on symbol or name (e.g. query='S&P 500'). Every filter accepts one value or several comma-separated values. Use show_options('indices', '') to see valid filter values.

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": "indices"
  }
}

Input Schema

Name	Required	Description
`mic`	No	ISO 10383 market identifier code, e.g. 'XNAS', 'XNYS' or 'XAMS'. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
`limit`	No	Rows to return (default 25, maximum 200).
`query`	No	Optional free-text search on symbol and name (case-insensitive substring, e.g. 'apple' or 'AAPL'); an ISIN also matches where available. Best matches come first.
`offset`	No	Rows to skip, for paging (see the `_notes` hint in the response).
`category`	No	Category, e.g. 'Large Cap', 'Bonds', 'Technology' or 'Emerging Markets'. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
`currency`	No	Trading currency as an ISO code, e.g. 'USD' or 'EUR'. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
`exchange`	No	Exchange code, e.g. 'NMS' (NASDAQ Global Select), 'NYQ' (NYSE), 'PNK' (OTC Markets) or 'AMS' (Euronext Amsterdam). Use it to find an instrument's listings on certain exchanges, e.g. query='ASML' with exchange='NMS,NYQ,PNK' for its US listings. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
`show_columns`	No	Columns to return, comma-separated. Default: symbol, name, currency, category_group, category, exchange. Available: symbol, name, currency, summary, category_group, category, exchange, mic.
`category_group`	No	Broad category group, e.g. 'Equities', 'Fixed Income', 'Commodities' or 'Information Technology'. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
`include_summary`	No	Add the business/fund description (truncated to 300 characters). Off by default to keep responses small.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.2/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 openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral trait beyond the annotations: every filter accepts either one value or several comma-separated values, which changes how an agent composes multi-value calls. It stops short of describing result ordering or response shape, but that is a minor gap given 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 short sentences, front-loaded with what the tool returns, then the multi-value convention, then the discovery pointer. No filler or redundant restatement of the name.

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 10 optional parameters, full schema coverage and no output schema, the description covers purpose, filter semantics and value discovery adequately. It could note default paging limits or hint at the returned columns, but show_columns and offset already document those in the schema.

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%, so each parameter already documents its format, defaults and examples. The description's only added semantic content is the global 'comma-separated multi-value' rule and the query example, both of which largely restate what the schema says per-parameter. 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?

Uses a specific verb ('List') plus a precise resource ('market indices') and enumerates the filter dimensions: category group, category, currency, exchange, and free-text query on symbol/name. The resource is unambiguous and clearly distinct from the sibling tools equities, etfs, cryptos and currencies.

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?

Gives a concrete usage example (query='S&P 500') and routes the agent to show_options('indices', '<field>') for discovering valid filter values, which is a real cross-tool instruction. It does not say when to prefer this over equities/etfs for instrument lookup, but the context is clear enough.

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

All Finance Database 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.