Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Price Adjustment Factors

get_adjustment_factors
Read-onlyIdempotent

Get the split/bonus adjustment-factor timeline for a stock, so a raw (unadjusted) price series can be reconstructed from the adjusted one. Returns per-event factor and cumulative factor with ex-dates, plus the reconstruction formula in meta. USE THIS when a price move looks impossibly large and you need to know whether it was a corporate action rather than a real return, or when the user asks for raw/unadjusted prices, or asks how to adjust for splits and bonuses. CRITICAL: the response also carries unquantified_events — rights issues and demergers that are KNOWN but have NO reliable numeric factor (a rights adjustment needs the subscription price; a demerger is not a single number). Never invent a factor for those; tell the user those ex-dates should be excluded or treated with caution. NOTE: data has split/bonus factors; rights factors are on REST corporate-adjustments. PRICE-return, not total-return.

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

Input Schema

NameRequiredDescriptionDefault
symbolNoREQUIRED. The stock symbol, e.g. "RELIANCE" or "TRENT".
tickerNoAlias for `symbol`.
identifierNoAlias for `symbol`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only cover safety (readOnly, idempotent, non-destructive), and the description goes well beyond them: it discloses that `unquantified_events` may contain rights issues and demergers with no numeric factor, warns against inventing one, and states the return basis is price-return rather than total-return. The only missing piece is guidance on empty/missing results for symbols with no corporate actions.

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?

The definition is front-loaded with purpose, then usage triggers, then the critical caveat, which is a sensible order. It is dense with capitalized emphasis (USE THIS, CRITICAL, KNOWN, NO) that aids scanning but makes it longer than strictly necessary.

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?

There is no output schema, and the description compensates by describing the returned fields (`data` with per-event and cumulative factors and ex-dates, the reconstruction formula in `meta`, and `unquantified_events`). Combined with the stated return basis and caveats, an agent has everything needed to call and interpret it.

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 coverage is 100% and the schema already documents `symbol` plus the `ticker`/`identifier` aliases, so the description carries no parameter burden. It adds no example values or clarification about which identifier form to prefer, which leaves it at the baseline for full schema coverage.

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?

Names a specific resource (split/bonus adjustment-factor timeline) and the exact outcome (reconstructing a raw price series from an adjusted one). This is clearly distinct from sibling tools like get_price_history (prices) and get_corporate_actions (event list) because it describes the factor/cumulative-factor payload.

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?

Explicit 'USE THIS when' triggers are given: an implausibly large price move, a request for raw/unadjusted prices, or a question about split/bonus adjustment. It also routes away from itself by stating that rights factors live on the REST corporate-adjustments resource.

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.