Skip to main content
Glama

TejHQ Indian Markets

Delivery quantity and percent

delivery
Read-onlyIdempotent

Daily traded volume, delivery quantity and delivery percent for one symbol. 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": "delivery"
  }
}

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description still adds genuinely useful behavior beyond that: 'Up to 250 rows per call, oldest first' discloses truncation and sort order, and 'End of day data only, no intraday or live prices' plus per-exchange coverage dates prevent wrong expectations about freshness. It does not explain what a truncated result looks like or how meta.next_offset is surfaced on a response, which keeps it short of a 4.

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?

Six short sentences, zero filler, and the core capability is front-loaded before constraints, coverage and auth. Every sentence carries a fact an agent needs: required fields, default window, row cap, ordering, data freshness, coverage dates, key requirement. Nothing is repeated from annotations.

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?

For a 6-parameter read-only time-series endpoint with no output schema, the description covers the essentials: required fields, default date range, row cap and ordering, data granularity, per-exchange coverage, and auth. The remaining gap is return-shape detail, such as what fields each row contains or how truncation is signalled, though no output schema exists to carry that instead.

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 one of the six parameters is already documented in the input schema, including defaults, formats and the meta.next_offset paging hint. The description's only parameter-level contribution is the 'oldest first' ordering, which the schema does not state, and a restatement of the 90-day default. That meets the high-coverage baseline of 3 rather than exceeding it.

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 opens with a specific verb and resource set: 'Daily traded volume, delivery quantity and delivery percent for one symbol.' An agent can immediately tell what data comes back and that the scope is a single symbol. It never names a sibling tool, though, so distinguishing it from ohlcv or snapshot is left to inference.

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 clear when-contexts: EOD-only data, no intraday or live prices, and the default 90-day window when from and to are omitted. It also states the delivery data coverage start dates per exchange and the API-key requirement, which are real prerequisites. What is missing is any explicit statement of when to prefer this tool over a sibling such as ohlcv or snapshot.

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