Skip to main content
Glama

Search Strategy Lists

tt_search_lists
Read-onlyIdempotent

Search the signed-in user's Tradetron instrument lists by name.

Call this whenever the user references a watchlist / universe / instrument basket by name ("my breakout list", "NIFTY 50", "the F&O smallcap list") so you can resolve it to a concrete numeric list_id BEFORE wiring it into a strategy. Also use to confirm a named list actually exists.

Returns own + public lists (metadata only): list_id, name, instrument_count, segment, exchange. Public/system lists (NIFTY 50, Banknifty, ...) are included so you can resolve them too. Restricted to IN exchanges. If several lists match, show them and ask the user which one.

AUTH-REQUIRED: returns the connect/sign-up funnel if the user hasn't connected their Tradetron account.

How the list_id is used downstream: a list-based set carries the integer list id at BOTH the set level and on every leg (with the leg's instrument=0). Put the resolved id in the Set identity's List: field — the emitter propagates it to the legs and the validator enforces the coupling.

Args: q: optional case-insensitive substring of the list name. Empty → all (capped by limit). limit: 1..100, default 20.

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_search_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
limitNoRows to return, 1..100. Default 20. A larger value is clamped to 100; below the minimum is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/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 the description adds substantial context beyond them: results include both own and public/system lists, metadata only, IN-exchange restriction, and an AUTH-REQUIRED funnel response when the account is unconnected. It even explains downstream coupling semantics (list id on both set and legs) that the agent cannot get from annotations.

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?

Content is front-loaded: purpose, trigger, return shape, then downstream mechanics. Some redundancy exists — the limit range/default appears in both the args block and the schema — and the downstream emitter/validator paragraph is dense, but each part still carries real routing value.

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 enumerates returned fields (list_id, name, instrument_count, segment, exchange), covers the auth failure mode, and explains how the returned id is consumed downstream. Nothing an agent needs to call this correctly or interpret its result is missing.

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 coverage is only 50% — q has no schema description — and the description fully compensates by defining it as an optional case-insensitive substring of the list name, with empty meaning all. For limit it restates the 1..100 range and default 20 plus the 'capped by limit' behavior, which mostly duplicates the schema rather than extending it.

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?

The opening sentence names a specific verb (Search) and resource (the signed-in user's Tradetron instrument lists) with an explicit matching key (by name). No sibling tool covers list resolution, and the description states the basic prerequisite goal (resolve a name to a numeric list_id) so the agent can tell exactly what this tool is for.

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?

It gives an explicit trigger ('whenever the user references a watchlist / universe / instrument basket by name'), a sequencing rule (resolve BEFORE wiring into a strategy), a secondary use (confirm a named list exists), and an ambiguity procedure (show matches and ask the user which one). That is when-to-use, why-to-use, and edge-case handling in one place.

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