Skip to main content
Glama

List Supported Underlyings

tt_list_underlyings
Read-onlyIdempotent

List underlyings Tradetron supports trading, with filters.

exchange: 'NSE' / 'NFO' / 'NASDAQ-EQ' / 'MCX' / ... . instrument_type: 'FUTSTK' / 'OPTSTK' / 'FUTIDX' / 'OPTIDX' / 'SPOT' / 'FUTCRYPTO' / ... .

CASH EQUITIES ARE NOT 'SPOT'. Tradetron's instrument_type codes are overloaded: a cash stock is stored as OPTSTK on a CASH exchange (NSE, NASDAQ-EQ), while OPTSTK on NFO/BATO is the option contract. 'SPOT' is FX and crypto reference prices only — overwhelmingly FX, which Tradetron does not trade at all. For "what stocks can I trade?" filter by EXCHANGE (exchange='NSE' for Indian cash, 'NASDAQ-EQ' for US), not by instrument_type.

Use this for "what stocks can I trade?" / "any index options?" / "do you have US equities?" type questions.

search: symbol prefix OR company/index name words ('RELI', 'Reliance Industries', 'Infosys') — the way to find a symbol from a name. Matching names come back in names. limit / offset: page through the sorted symbol list (limit max 500). When truncated=True, next_offset is the offset for the next page.

The catalog has thousands of symbols. Answer "what stocks can I trade?" with the counts and breakdowns plus a page — do not page through everything unless the user asks for the full list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tt_list_underlyings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNo
exchangeNo
instrument_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds material behavior on top: catalog size in the thousands, limit capped at 500, and the truncated/next_offset pagination contract including the `names` field for matched search terms. That is exactly the context the annotations cannot carry.

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?

Long but dense and front-loaded, with each block (codes, the cash-equity trap, search, pagination, catalog-size advice) earning its space given zero schema coverage. The capitalization-heavy warning about 'SPOT' repeats the same point twice, which costs a little tightness.

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?

Covers filtering traps, name-to-symbol search, pagination and the correct way to answer a catalog question, which is everything an agent needs for a 5-param, 0%-coverage list tool with no output schema. The overloading of `instrument_type` is called out precisely where an agent would otherwise misfilter.

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 description coverage is 0% and no parameter is an enum, yet the description supplies the allowed value families for `exchange` and `instrument_type`, the prefix/name-word semantics of `search`, and the paging role of `limit`/`offset`. The only shortfall is that the code lists are open-ended ('...'), so some valid values remain undiscoverable.

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?

Opens with a specific verb and resource ('List underlyings Tradetron supports trading, with filters'), so an agent knows exactly what it returns. It does not name a sibling tool it differs from (e.g. tt_check_underlying_support for a single-symbol check), so sibling differentiation is left implicit.

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 concrete user-question triggers ('what stocks can I trade?', 'any index options?', 'do you have US equities?') and an operational rule: answer with counts and a page rather than paging through everything. What is missing is an explicit statement of when NOT to use it or which alternative tool handles single-symbol support checks.

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