Skip to main content
Glama
Tapetide - Indian Stock Market MCP

Tapetide - Indian Stock Market MCP

Resolve a Symbol/ISIN As-Of a Date

resolve_identifier_asof
Read-onlyIdempotent

Resolve a historical NSE symbol or ISIN to the company that held it on a given date, so old holdings, research notes, or backtests map identifiers correctly despite renames, reuse, or delistings.

Instructions

Resolve a historical symbol or ISIN to the company that held it ON a given date. USE THIS when working with old data whose ticker may since have been renamed, reused, or reassigned — e.g. a 2018 holdings file, an old research note, or a backtest that must not treat one company as two securities (or worse, merge two different companies because a ticker was recycled after a delisting). Returns present | uncertain | not_found | out_of_coverage with certainty ranges. uncertain means the date falls in an open bracket around a rename/ISIN change — quarantine it rather than asserting the mapping. The response states its own coverage window; a date outside it returns out_of_coverage and must not be reported as 'no such symbol'.

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

Input Schema

NameRequiredDescriptionDefault
dateNoAs-of date, YYYY-MM-DD. Defaults to today (IST) when omitted.
kindNoWhich identifier kind `value` is (default nse_symbol)nse_symbol
valueNoREQUIRED. The identifier value, e.g. "TRENT" or "INE849A01020".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.9

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare only the safety profile (readOnly, idempotent, non-destructive); the description goes well beyond that by enumerating the four return states, defining `uncertain` semantics (open bracket around a rename/ISIN change), advising quarantine rather than assertion, and warning that coverage is self-reported. This is exactly the extra behavioral context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then usage trigger, then return semantics — a logical progression. No filler sentences; the emphatic caps guide attention on the two genuine hazards (merging recycled tickers, mislabeling out-of-coverage as not-found).

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?

With no output schema, the description carries the burden of explaining returns and it does so — enumerating all four statuses and what each implies for downstream handling. An agent has everything needed to call it and interpret the result 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?

Schema coverage is 100%, so a baseline of 3 applies, but the description adds meaning the schema does not: it explains why `date` matters (point-in-time identity, not just a format string) and frames `value`/`kind` as a symbol or ISIN pair. The add-value over the schema is real though modest.

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?

Specific verb+resource+scope: 'Resolve a historical symbol or ISIN to the company that held it ON a given date.' The point-in-time qualifier ('as-of') distinguishes it from plain lookup siblings like search_stocks or get_identifiers_asof, and the description makes the temporal dimension the core of the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicit when-to-use with concrete scenarios (2018 holdings file, old research note, backtest that must not merge recycled tickers). It also gives a when-NOT-to-act instruction ('must not be reported as no such symbol' for out-of-coverage dates). It does not explicitly name an alternative sibling (e.g. get_identifiers_asof) to route the agent, so it stops short of a 5.

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