Skip to main content
Glama

TejHQ Indian Markets

Symbol history

symbols
Read-onlyIdempotent

Ticker history on one exchange: which symbol an ISIN traded under, and over which dates. Use it to follow renames. Required: exchange, and one of symbol or isin. 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>"
    },
    "name": "symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinNoISIN to look up, for example INE002A01018. Pass this or symbol.
limitNoMost rows to return.
offsetNoRows to skip, for paging. Use meta.next_offset from a truncated result.
symbolNoTicker to look up. Pass this or isin.
exchangeYesExchange: nse or bse, lower case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses data granularity (end of day only, no intraday or live), per-exchange coverage start dates (NSE 2010-01-04, BSE 2024-07-08), and the auth tier requiring a free API key with a URL. These are exactly the operational constraints 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core purpose, then requirements, then data limits, then coverage and auth. No filler and nothing buried.

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 conveys what comes back (symbol and date range per ISIN), and it covers coverage windows, granularity, and auth. Nothing material is missing for correct invocation.

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 in the schema, including the 'pass this or isin' exclusivity and the enum values. The description only restates the required combination, adding no new syntax or format meaning, so the baseline 3 applies.

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 verb and resource: ticker history on one exchange, mapping an ISIN to the symbol it traded under and the date range. The phrase 'Use it to follow renames' pins down the intent so an agent can distinguish it from a plain symbol-to-ISIN resolver.

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 when-to-use guidance ('follow renames') and restates the required inputs (exchange plus one of symbol or isin). It does not explicitly name a sibling alternative such as resolve or say when not to use it, so it stops short of full routing guidance.

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