Finance Database

etfs

Read-onlyIdempotent

List exchange-traded funds matching filters such as category group, category, family (issuer), currency and exchange, or matching a free-text query on symbol or name. Every filter accepts one value or several comma-separated values. Use show_options('etfs', '') 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": "etfs"
  }
}

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.
`family`	No	Fund family (issuer), e.g. 'BlackRock Asset Management' or 'Vanguard Asset Management'. Use show_options to find the exact name. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
`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, family, exchange. Available: symbol, name, currency, summary, category_group, category, family, exchange, mic, isin, delisted.
`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.
`include_delisted`	No	Include delisted entries (excluded by default). Adds a `delisted` column.
`only_primary_listing`	No	Only primary listings: per instrument its listing on the main exchange of its home market (ASML.AS for ASML), or without one its listing on the largest main exchange abroad. Leaves out cross-listings, over-the-counter lines and depositary receipts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.7/5.0

Behavior3/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 the multi-value filter convention and the show_options discovery path, but says nothing about result ordering (beyond 'best matches first' for query, which lives in the schema), paging, or default exclusions such as delisted entries. Adequate given the annotation coverage, but not rich.

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?

Three sentences, front-loaded with purpose and scope, with no filler or marketing language. The middle sentence about comma-separated values largely duplicates the schema and is the only slightly wasted line.

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 13-parameter read-only listing tool with fully documented schema and no output schema, the description covers purpose, filter surface, and value discovery. Paging behavior and delisted-by-default are left to the schema, which documents them clearly, so nothing critical is missing for a correct call.

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 the schema already documents every one of the 13 parameters including examples and defaults. The description's claim that 'every filter accepts one value or several comma-separated values' restates what each schema property already says, adding no new meaning. Baseline 3 applies where the schema does all the work.

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 ('List exchange-traded funds') and enumerates the filter dimensions (category group, category, family, currency, exchange, free-text query). The resource is unambiguous against siblings like equities, cryptos and indices, so an agent can pick this tool 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 Guidelines3/5

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

Gives one concrete routing instruction: call show_options('etfs', '<field>') to discover valid filter values, which is genuinely useful. However it offers no guidance on when to choose this tool versus equities, indices, or search_instruments, and no prerequisites or exclusions are stated. Usage is implied by the resource name rather than explained.

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.