TickerDB

get_index_members

Read-only

An index's members on one date, point in time: the long stock positions of its tracking fund's newest SEC N-PORT portfolio FILED by that date (source.report_date is the portfolio's own quarter-end date, source.filed_on when it became public; a stock added to the index after report_date appears with the next filing). Each member has ticker (as of the date), name and weight_pct (percent of fund net assets). Ids from get_indexes. To screen members by fields, use get_universe or get_search with member_of instead. Costs 1 credit plus 1 per 100 members beyond 100.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "index": "<index>"
    },
    "name": "get_index_members"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No	Date YYYY-MM-DD (default today). History depth depends on plan.
`index`	Yes	Index id from get_indexes, e.g. "sp500", "nasdaq100", "russell2000".

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?

Beyond the readOnly/openWorld annotations, it discloses the data provenance and lag semantics (report_date is the portfolio quarter-end, filed_on the public date; an addition after report_date appears only in the next filing) — a real behavioral trait an agent must know. It also gives an exact cost model ('1 credit plus 1 per 100 members beyond 100'), which is not captured anywhere else.

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?

It is front-loaded with the core definition and every sentence carries information (provenance, fields, alternatives, cost). The long nested parenthetical about report_date/filed_on is dense and slightly slows parsing, but nothing is wasted.

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?

For a two-parameter read tool with an output schema, annotations, and full schema coverage, everything an agent needs is present: what is returned, the temporal semantics, id sourcing, alternatives for filtering, and cost. Return-value detail is a bonus rather than a requirement given the output schema exists.

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 the baseline is 3, but the description adds genuine meaning: it ties the date parameter to filing-lag behavior and clarifies that ticker is 'as of the date' and weight_pct is a percent of fund net assets. The only gap is that it doesn't restate the YYYY-MM-DD format or the plan-dependent history depth, which the schema already covers.

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 opens with a concrete verb and resource ('An index's members on one date') and then precisely defines what membership means here — the tracking fund's newest SEC N-PORT long stock positions filed by that date — which is far more specific than the tool name alone. It also names the sibling tools (get_universe, get_search with member_of) that handle the adjacent task, so an agent can tell it apart at a glance.

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?

It states the selection rule explicitly: use this tool for point-in-time index membership, and use get_universe or get_search with member_of when screening members by fields. It also routes the agent to get_indexes for the required id, covering both the 'when' and the prerequisite.

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.