TickerDB

get_indexes

Read-only

List the indexes whose membership TickerDB tracks (sp500, sp400, sp600, sp100, nasdaq100, russell1000, russell2000), each with the fund it is read from (e.g. IVV for the S&P 500), its first covered date (late 2019) and today's member count. Membership is the SEC Form N-PORT holdings of a fully replicating fund, point in time by filing date: typically 2-5 months behind the index provider's own changes. Use the ids with get_index_members, or as member_of in get_universe / get_search. Costs 1 credit.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	No	The TickerDB API response payload for this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes well beyond that by disclosing the data source (SEC Form N-PORT holdings of a fully replicating fund), the point-in-time-by-filing-date semantics, and a concrete 2-5 month lag versus index providers. It also states a cost of 1 credit, which no annotation conveys.

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?

Front-loaded with purpose and the id list, then the caveats and the follow-up routing. Two of the parentheticals (the index list and the IVV example) run long, but each sentence still carries information an agent needs to pick this tool and interpret the lag.

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?

An output schema exists, so return values need not be re-documented, yet the description still summarizes the key fields. Combined with the no-params schema, read-only annotations, and the explicit next-step routing, an agent has everything needed to call this correctly.

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?

The tool takes zero parameters, so the baseline is 4. The description nonetheless clarifies the shape of the returned records (fund source, first covered date of late 2019, today's member count), which frames what the ids mean without needing parameter explanation.

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 the indexes') and enumerates the exact identifiers it returns (sp500, sp400, ...). It is clearly distinguishable from siblings like get_index_members, which it explicitly references as the next step.

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 tells the agent how to use the results: 'Use the ids with get_index_members, or as member_of in get_universe / get_search.' It names the alternatives and the condition that connects them, leaving nothing to inference.

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

All TickerDB 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.