Skip to main content
Glama

TejHQ Indian Markets

Daily derived metrics

metrics
Read-onlyIdempotent

Daily computed metrics for one symbol: adj_close, returns over 1, 5, 21, 63, 126 and 252 days and year to date, 52-week high and low and distance from them, average volume and turnover. 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 Retail or Pro key (https://tejhq.dev/upgrade).

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

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.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the description is free to add genuinely new behavior: default 90-day window, 250-row-per-call truncation, oldest-first ordering, EOD-only freshness, per-exchange coverage start dates, and a required Retail/Pro key with an upgrade link. Auth tier, freshness, and result-ordering are exactly the traits an agent cannot get from the annotations or schema.

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?

One dense, front-loaded paragraph that opens with what the tool returns, then prerequisites, defaults, limits, freshness, coverage, and access tier in that order. The field enumeration is long but every item carries information an agent needs; there is no filler.

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 does the necessary work by naming the returned metrics, the row cap and ordering, and the data coverage window. The only gap is the response envelope: the schema references meta.next_offset for paging, but the description never mentions that the result carries a meta block, leaving an agent to discover it from the schema field.

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 from, to, limit, offset, symbol, and exchange are already fully documented in structured form. The description adds only the default-window behavior tied to from/to, which is already implied by the schema defaults, and says nothing new about limit/offset paging semantics. Baseline 3 is appropriate.

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?

The description gives a specific resource (daily derived metrics for one symbol) and enumerates the exact fields returned: adj_close, 1/5/21/63/126/252-day and YTD returns, 52-week high/low and distance, average volume and turnover. That enumeration clearly separates it from a raw price feed like ohlcv, but it never names the sibling it is not, so the differentiation is inferential rather than stated.

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?

It gives concrete operating context: required parameters, that omitting from/to yields the last 90 days, 250-row cap, oldest-first ordering, EOD only with no intraday or live prices, and coverage start dates per exchange. What it lacks is routing guidance — there is no explicit statement of when to prefer this over a sibling such as ohlcv or adjusted, or when this tool is the wrong choice.

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