Skip to main content
Glama

FinanceQuery

Index Constituent Changes

get_index_constituent_changes
Read-onlyIdempotent

Get additions and removals from an index's constituent list.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_index_constituent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesIndex symbol (e.g. ^GSPC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety and side-effect profile is covered. The description adds no behavior beyond that: it does not say how far back changes go, whether ordering is chronological or reverse-chronological, or that results are paginated. With annotations doing the heavy lifting this is a modest gap, not a fatal one.

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?

One sentence, front-loaded with the verb and the distinguishing resource ('additions and removals'). No filler or redundancy, though it is arguably too thin rather than merely concise.

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 four-parameter read-only lookup with a fully documented schema and no output schema, the core intent is conveyed and nothing an agent needs to call it is strictly missing. The remaining gap is that the description does not characterize the returned change records (fields, time span) or that pagination applies, which would have made it complete for a changes-feed tool.

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%, and each parameter (symbol, limit, cursor, fields) is fully documented in the schema including defaults and token provenance. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb ('Get') and resource ('additions and removals from an index's constituent list'), which is meaningfully distinct from a plain constituents fetch. It does not explicitly name get_index_constituents as the contrasting sibling, so the differentiation is only implicit.

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?

The word 'changes' implies this is the tool for historical membership edits rather than the current constituent roster, which lightly routes the agent. There is no explicit statement of when to use this versus get_index_constituents, nor any prerequisite (e.g., that a valid index symbol is required).

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.