Skip to main content
Glama

TejHQ Indian Markets

One day, whole exchange

snapshot
Read-onlyIdempotent

Every symbol's bhavcopy line for one trading date on one exchange, about 3,000 rows in full. Required: exchange, date. Returns 50 rows by default, up to 200, sorted by turnover, largest first. Filter with symbols or series and change the order with sort_by. meta.total counts rows after filters. Weekends and holidays have no rows; use status for the latest date. 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>",
      "date": "<date>"
    },
    "name": "snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesTrading date. Format YYYY-MM-DD.
limitNoMost rows to return.
offsetNoRows to skip, for paging. Use meta.next_offset from a truncated result.
seriesNoOnly this series, for example EQ on NSE. Case does not matter.
sort_byNoSort key. Numeric keys sort largest first; symbol sorts A to Z. change_pct is close against prev_close. Default turnover.
symbolsNoReturn only these symbols.
exchangeYesExchange: nse or bse, lower case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read; the description adds real behavior beyond them — default 50 rows, 200 cap, turnover-largest-first ordering, meta.total counting after filters, no rows on weekends/holidays, and historical coverage start dates per exchange. The 'no API key needed' note further lowers invocation friction.

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 what the tool returns and its scale, then requirements, limits, filtering, edge cases, and coverage — each sentence carries distinct information with no filler.

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 explains the shape of results (rows sorted by turnover, meta.total, meta.next_offset-driven paging implied by the schema) and covers the empty-result cases and historical bounds an agent needs to call it 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 the baseline is 3, but the description adds cross-parameter meaning the schema does not: meta.total counts post-filter rows and results are truncated at 200, which tells the agent how filters and paging interact. It restates required exchange/date but adds little else per-parameter beyond the schema.

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?

Opens with a precise verb+resource+scope: every symbol's bhavcopy line for one trading date on one exchange. It explicitly excludes intraday/live prices, which separates it from ohlcv-style siblings, and quantifies scope (~3,000 rows in full).

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?

States concrete when-to-use conditions: end-of-day data only, and 'use status for the latest date' names the alternative for that need. It doesn't explicitly name a sibling to use for intraday prices, but the exclusion is clear enough that the agent knows not to call this for live 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