Skip to main content
Glama

TejHQ Indian Markets

Daily prices (unadjusted)

ohlcv
Read-onlyIdempotent

Daily open, high, low, close, last, previous close, volume, turnover and trades for one symbol on one exchange, as printed in the exchange bhavcopy, not adjusted for splits or bonuses. Use adjusted for continuous price history. 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. No API key needed.

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

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.4/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, closed-world), and the description adds real context beyond them: unadjusted values, oldest-first ordering, 250-row cap per call, 90-day default window, coverage start dates per exchange, and no auth requirement. It stops short of describing the response envelope or truncation signaling, but that is a minor gap given the annotation coverage.

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 payload contents, then constraints, then coverage — a logical order with no filler sentences. The opening field enumeration is dense but each item is substantive; nothing is redundant with the schema except the date-default restatement.

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?

For a read-only historical-price tool with no output schema, the description supplies everything an agent needs to call it correctly and interpret scope: units of the row limit, ordering, default window, exchange coverage start dates, and the no-intraday boundary. Nothing material is left to inference.

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 description coverage is 100%, so every parameter is already documented, including the from/to defaults, limit maximum, and offset paging via meta.next_offset. The description's 'Without from and to it returns the last 90 days' largely restates the schema's default and adds no syntax or format detail beyond it.

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 resource (daily OHLC + last, prev close, volume, turnover, trades) for one symbol on one exchange, and pins down the unadjusted nature ('as printed in the exchange bhavcopy, not adjusted for splits or bonuses'). This directly differentiates it from the sibling 'adjusted' tool without the agent needing to open 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?

Explicitly routes to the alternative ('Use adjusted for continuous price history') and states an exclusion ('End of day data only, no intraday or live prices'). Defaults for the date window and row cap are given inline, so the agent knows what happens when optional params are omitted.

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