Skip to main content
Glama
Tapetide - Indian Stock Market MCP

Tapetide - Indian Stock Market MCP

Identifiers Held By a Stock As-Of a Date

get_identifiers_asof
Read-onlyIdempotent

Resolve a stock_id and as-of date to the symbol and ISIN a company held then. Use it to label historical backtests or explain ticker changes.

Instructions

The REVERSE of resolve_identifier_asof: given a stock_id and a date, return which symbol and ISIN that company held at that time. USE THIS to label historical output correctly — e.g. reporting a 2019 backtest position under the ticker it actually traded as then, rather than its current name. Also useful for explaining a rename to a user who is confused why a symbol they remember no longer resolves. stock_id comes from other tools' meta.stock_id; this tool does not accept a symbol. Coverage bounds are stated in the response — outside them the answer is out_of_coverage, not 'no identifiers'.

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

Input Schema

NameRequiredDescriptionDefault
dateNoAs-of date, YYYY-MM-DD. Defaults to today (IST) when omitted.
stock_idNoREQUIRED. The internal stock id, as returned in other tools' meta.stock_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.9

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's burden is lighter; it still adds real behavior: stock_id must come from meta.stock_id and symbols are rejected, and out-of-range dates yield an `out_of_coverage` sentinel rather than an empty result. That sentinel semantics is the most valuable disclosure here and is not present in the schema or annotations.

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 the core purpose and the reverse-of relationship, then usage, then coverage caveat. It is on the longer side and the 'explaining a rename to a user' clause is marginally expendable, but each sentence carries actionable information.

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?

With no output schema, the description takes responsibility for the return contract by naming the returned fields (symbol and ISIN) and the out_of_coverage sentinel. An agent can invoke and interpret this tool without guessing; only the exact response shape/pagination is unspecified, which is a minor gap.

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 meaning beyond the schema: it states stock_id's provenance is other tools' meta.stock_id and — importantly — that the tool does not accept a symbol, guarding against a plausible misuse. Date defaulting is already in the schema and is not repeated, keeping the added value focused.

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 precise verb+resource ('return which symbol and ISIN that company held at that time') and explicitly frames itself as 'the REVERSE of resolve_identifier_asof', which cleanly distinguishes it from its nearest sibling. The stock_id/date inputs are named, so an agent knows exactly what it consumes.

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 two concrete when-to-use scenarios (labelling historical backtest output under the historical ticker; explaining a rename to a confused user) and implicitly contrasts with the forward resolving tool. Nothing about when this tool applies is left to inference.

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