Skip to main content
Glama

TejHQ Indian Markets

Back-adjusted daily prices

adjusted
Read-onlyIdempotent

Daily prices for one symbol back-adjusted for corporate actions, with the cumulative adjustment factor and adj_close. Required: exchange, symbol. Without from and to it returns the last 90 days. Up to 250 rows per call, oldest first. End of day data only, no intraday or live prices. Coverage: NSE from 2010-01-04, BSE from 2024-07-08. Tier: needs a free API key (https://tejhq.dev/keys).

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

Input Schema

NameRequiredDescriptionDefault
toNoLast date, inclusive. Default: today. Format YYYY-MM-DD.
fromNoFirst date, inclusive. Default: 90 days before to. Format YYYY-MM-DD.
limitNoMost rows to return.
offsetNoRows to skip, for paging. Use meta.next_offset from a truncated result.
symbolYesExchange ticker, for example RELIANCE, TCS, M&M. Case does not matter.
exchangeYesExchange: nse or bse, lower case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: it discloses the 250-row cap, oldest-first ordering, the 90-day default window, exchange coverage start dates, and that a free API key is required. These are exactly the operational facts an agent needs before calling.

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-loads the return content, then constraints, then coverage and auth in a compact run of short sentences. 'Required: exchange, symbol' duplicates the schema's required list, a minor redundancy in an otherwise dense definition.

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 still names the key returned fields, and it covers defaults, row caps, ordering, coverage, and auth. Nothing material is missing for a 6-parameter read-only endpoint.

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 description coverage is already 100%, so the baseline is 3; the description adds the combined-parameter behavior ('without from and to it returns the last 90 days') and reaffirms the required pair. It doesn't explain limit/offset interaction beyond what the schema already says.

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?

Names a specific verb+resource ('Daily prices for one symbol back-adjusted for corporate actions') and states what comes back (cumulative adjustment factor, adj_close). It also excludes intraday and live data, which separates it from snapshot-style siblings, though it never names an explicit alternative like ohlcv.

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?

Gives clear context for when the tool applies (EOD only, back-adjusted, per-symbol) plus coverage windows (NSE from 2010-01-04, BSE from 2024-07-08) and the auth prerequisite. It stops short of naming a sibling to use instead when the agent wants raw/unadjusted or intraday data.

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.

Resources