Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Index Memberships of a Stock

get_stock_index_memberships
Read-onlyIdempotent

Every tracked index a stock has been in, one row per membership spell with its start, end and the dates bounding each join and exit. Each index's record has its own start (the earliest is meta.coverage_from), so an empty list means no tracked index since its record began, not never; joined_before_coverage: joined before the record. For one index on one date use get_index_membership_asof. With date, empty means not a member only when meta.date_status is in_coverage; partial_coverage answers only meta.covered_indices.

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_stock_index_memberships"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOnly spells containing this date, YYYY-MM-DD.
cursorNo`meta.next_cursor` from the previous call; repeat the other arguments.
symbolNoREQUIRED. Stock symbol, e.g. "DIXON".
tickerNoAlias for `symbol`.
identifierNoAlias for `symbol`.
include_uncertainNoWith `date`, also spells whose join or exit bracket contains it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description goes well beyond them by disclosing coverage behaviour: per-index record start, `meta.coverage_from`, the `joined_before_coverage` flag, and the in_coverage vs partial_coverage distinction for dates. These are exactly the caveats an agent needs to avoid misreading an empty list.

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?

Well front-loaded — the core behaviour leads, then coverage caveats, then the sibling routing. The middle sentences are semicolon-heavy and jargon-dense ("the dates bounding each join and exit", "joined_before_coverage"), costing some first-read clarity.

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?

No output schema exists, so the description carries the return-shape burden and does so by describing row-per-spell output plus the `meta` fields that govern interpretation. Minor gaps: pagination via `cursor`/`meta.next_cursor` and the note that `symbol` is REQUIRED appear only in the schema, not the prose.

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; the description earns extra by adding meaning to `date` that the schema does not (empty means 'not a member' only under in_coverage, and partial coverage answers only `meta.covered_indices`). It adds nothing for `include_uncertain`, `cursor`, or the symbol aliases, which the schema already documents.

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+resource: every tracked index a stock has been in, returned as one row per membership spell with start/end and join/exit bounding dates. It explicitly distinguishes itself from get_index_membership_asof, so an agent can route without opening either schema.

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?

Gives an explicit alternative and the condition that selects it: 'For one index on one date use get_index_membership_asof.' It also tells the agent how to interpret an empty result, with a distinct rule for the `date` case gated on `meta.date_status` being in_coverage.

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.