Skip to main content
Glama

List Subscription Plans

tt_list_plans
Read-onlyIdempotent

List Tradetron's subscription plans with pricing + any live discounts.

NO SETUP NEEDED beyond the one-time sign-in — no broker, paid plan, or strategy data. Use this for "what plans does Tradetron offer?", "how much is the annual plan?", "any discounts?", or when comparing tiers for a prospect. Returns ONE row per distinct plan (the upstream lists each plan once per exchange; duplicates are merged — a plan's exchanges lists its venues and variants, when present, carries per-exchange differences) with its monthly / quarterly / yearly price, what it unlocks (strategy/deploy/backtest limits, execution mode, python, API), and active coupons.

NOTE — two separate backtest allowances exist; do not conflate them when answering: a plan's backtest_allowed limit governs backtests run from the WEBSITE's own Backtest button, while backtests run through THIS chat/MCP are billed per run from the Tradetron wallet (see tt_wallet_balance for the price) regardless of the plan limit.

TAX: India prices EXCLUDE GST; 18% GST is added at checkout (tax_note). Never say an India price includes tax or GST.

country: 'IN' / 'US' to filter pricing; None for the default.

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

Input Schema

NameRequiredDescriptionDefault
countryNo'IN' or 'US' to filter pricing; omit for the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 still adds substantive behavior: the upstream duplicate-per-exchange listing with merged rows, the meaning of the `exchanges` and `variants` fields, and that India prices exclude 18% GST with a `tax_note`. The backtest-allowance note prevents an agent from conflating plan limits with per-run MCP billing.

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?

Structure is strong — purpose first, prerequisites, use cases, return shape, then two flagged caveats (backtest allowances, GST) that earn their space by preventing wrong answers. It runs long with a couple of restated lines, but no sentence is filler in the way that would drop it below 4.

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?

For a single-parameter read tool with no output schema, the description covers both what is returned per row (prices, unlocked limits, coupons, exchanges/variants) and the two domain traps (backtest billing, GST). An agent has everything needed to answer correctly without a follow-up call.

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% and there is only one optional parameter, so the schema already carries the semantics; the description restates 'IN'/'US' filtering and adds that omitting it yields the default. That is consistent but adds little beyond the schema, 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?

The description opens with a specific verb+resource ('List Tradetron's subscription plans with pricing + any live discounts') and explicitly scopes it as a catalog view rather than the caller's own subscription, which separates it from tt_get_my_subscription.

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?

It gives concrete trigger phrasings ('what plans does Tradetron offer?', 'how much is the annual plan?', 'any discounts?') and the prospect-comparison scenario, plus prerequisite clarity via 'NO SETUP NEEDED beyond the one-time sign-in'. It does not explicitly route the 'what am I currently paying for' case to tt_get_my_subscription, which is the one nearby alternative an agent could confuse.

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