Skip to main content
Glama

Edit Strategy List

tt_modify_list
DestructiveIdempotent

Add or remove underlyings on one of the user's own instrument lists.

Address the list by NAME, exactly as the user says it ("add HDFCBANK to my breakout list") — list names are unique per user, so a list_id is not required and a prior tt_search_lists lookup is unnecessary. Matching is case-insensitive.

Only lists the user OWNS can be edited. Public/system lists (NIFTY 50, Banknifty, ...) are read-only and return a clear refusal — offer to create the user their own copy instead — noting that NO tool here creates or copies a list, so that offer means walking them through doing it on tradetron.tech, not doing it for them.

Args: list_name: the list's name as the user refers to it. add: symbols to add, e.g. ["HDFCBANK", "SBIN"]. remove: symbols to remove, e.g. ["INFY"]. list_id: only as a tie-breaker if two of their lists share a name (the tool tells you when that happens). exchange: override for resolving ADDED symbols. Leave empty — it defaults to the list's own exchange, which is right almost always. dry_run: resolve and report the would-be change without writing.

Reporting back: the result carries a ready-made summary line plus added, removed, already_present, not_present, unresolved, and count_before/count_after. Always tell the user about unresolved symbols (not tradable on that exchange) — silently dropping them is how a universe ends up smaller than intended.

The change reaches the live engine immediately, so a deployed list-based strategy starts trading the new members on its next evaluation. Say so when the list is in use.

AUTH-REQUIRED: returns the connect funnel when no Tradetron account is connected.

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

Input Schema

NameRequiredDescriptionDefault
addNo
removeNo
dry_runNo
list_idNo
exchangeNo
list_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is known. The description adds genuinely useful behavior beyond that: public lists return a clear refusal, added/removed symbols hit the live engine on the next evaluation, and an unauthenticated call returns a connect funnel. It does not, however, say whether a remove of a non-member is a no-op versus an error, or what the refusal/error shape looks like, so it stops short of full disclosure for a destructive mutation.

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?

Well front-loaded — purpose, then addressing rule, then ownership constraint, then args, then reporting, then side effects. The parenthetical about there being no create/copy tool is useful but runs long, and the emphatic capitalization plus nested asides make it denser than it needs to be.

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?

With no output schema, the description steps in and enumerates the returned fields (summary, added, removed, already_present, not_present, unresolved, count_before/count_after) and tells the agent to surface unresolved symbols. Missing only the failure/refusal payload shape, which matters given destructiveHint=true.

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 description coverage is 0%, so the description carries the full burden and does: list_name (case-insensitive, as the user says it), add/remove with example arrays, list_id as a tie-breaker only when names collide, exchange as an override for added symbols that defaults to the list's exchange, and dry_run as resolve-and-report-without-writing. That is meaning well beyond the bare property names.

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?

Opens with a specific verb pair plus resource and scope: "Add or remove underlyings on one of the user's own instrument lists." The ownership qualifier immediately separates it from read-only siblings like tt_get_list and tt_search_lists.

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?

Explicitly tells the agent to address the list by name and that a prior tt_search_lists lookup is unnecessary, which is a direct when-not-to-use instruction for a sibling. It also names the alternative path for public/system lists (walk the user through creating their own copy on the website) and states that no tool here copies lists.

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