Skip to main content
Glama

Check Underlying Support

tt_check_underlying_support
Read-onlyIdempotent

Check whether Tradetron supports trading a given underlying.

Deterministic lookup against the bundled underlying catalog (snapshot of TT's underlying table). Use this BEFORE answering any "can I trade X?" / "is X tradable?" / "is X listed?" question — it is authoritative. Do NOT guess from training data; if a symbol is not in this catalog, Tradetron does not support trading it.

Matching is case-insensitive and alias-aware: 'nifty' / 'NIFTY 50' / 'Nifty50' all collapse to the same canonical symbol; 'BANKNIFTY' resolves to 'NIFTY BANK'.

Returns: supported: True if at least one match exists. resolved_to: canonical symbol when the input was an alias. matches: [{symbol, exchanges, instrument_types, lot_sizes, kinds, emitter_buildable}]. kinds is the field that tells a CASH equity from a derivative — an equity typed OPTSTK is not an option, and nothing else in the response says so. emitter_buildable (also at top level) says whether the builder can author a leg on it. Both were returned undocumented. message: one-liner safe to relay to the user. may_be_a_name: true when the query looks like a company or index NAME rather than a ticker — do not report it as unsupported. symbol_candidates: on a miss, symbols whose company/index NAME matches the query ("Reliance Industries" → RELIANCE) — re-check the intended one by symbol. synthesis_instructions: guidance for you, not text for the user.

For listing all underlyings (e.g. "what stocks are on Tradetron?" or "which index options can I trade?") use tt_list_underlyings.

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": {
      "symbol": "<symbol>"
    },
    "name": "tt_check_underlying_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered; the description adds what annotations cannot — that this is a static snapshot lookup (staleness implications), that matching is case-insensitive and alias-aware with concrete collapse examples, and the non-obvious semantics of `kinds` and `emitter_buildable`. It also warns that `synthesis_instructions` is agent guidance rather than user-facing text, which is a genuinely useful behavioral disclosure.

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?

Front-loaded with purpose, then usage rule, then matching semantics, then a structured Returns block — good hierarchy with no wasted preamble. The parenthetical 'Both were returned undocumented' reads as a changelog aside rather than operative guidance and could be cut; the returns block is long but each field earns its place given there is no output schema.

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 supplies the full return shape field by field, plus the miss-path behavior (`may_be_a_name`, `symbol_candidates`) that an agent would otherwise misreport as unsupported. For a single-parameter lookup tool of this complexity, nothing needed to call it or interpret results is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single `symbol` parameter, so the description must carry the burden and does: it specifies case-insensitivity, alias resolution ('nifty'/'NIFTY 50'/'Nifty50' collapse; 'BANKNIFTY' → 'NIFTY BANK'), and that the input may be a company or index name rather than a ticker. That is meaning well beyond a bare `title: Symbol` field.

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 ('Check whether Tradetron supports trading a given underlying') and immediately characterizes the mechanism as a deterministic lookup against a bundled catalog snapshot. It also distinguishes itself from the sibling tt_list_underlyings by naming that tool for the enumeration case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit triggering conditions ('Use this BEFORE answering any "can I trade X?" ... question'), an explicit prohibition ('Do NOT guess from training data'), the negative inference rule (not in catalog = not supported), and a named alternative for listing. This is the full when/when-not/alternative triad.

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