Skip to main content
Glama

Tradetron Wallet Balance

tt_wallet_balance
Read-onlyIdempotent

Show the user's Tradetron wallet balance, what a backtest costs, and a clickable link to add funds.

Backtests are charged to the Tradetron wallet. Use this when the user asks about their balance, asks how much a backtest costs, says they are out of funds, or asks how to add funds (for example after a run was refused for insufficient balance): it returns the actual top-up link, so give that rather than a general 'add funds on the website'.

Returns {wallet_balance, backtest_price, backtests_affordable, backtests_affordable_from_wallet, topup_url?, backtest_pack?}. The two affordable keys are the SAME figure — the second is the honest name and the first is kept for callers pinned to it; quote either, never both as if they were different answers. topup_url is minted per call and legitimately differs between two reads a minute apart: it is a link to follow, not an identifier to compare. LEAD WITH backtest_pack WHEN IT IS PRESENT: an account holding a prepaid pack spends CREDITS first, so its runs cost ₹0 and this cash balance never moves — backtests_affordable is a cash-only figure and describes a payment path that account is not using. spendable_now is what a run today can actually draw; it is 0 on a pack whose billing cycle has ended, which is a different answer from "no pack" and must be said as such. Relay the balance verbatim; never invent or estimate a figure. If the balance could not be read, say exactly that.

NOTE: this wallet fee applies to backtests run through the chat/MCP. It is SEPARATE from a subscription plan's backtest_allowed limit, which governs the website's own Backtest button — a large plan allowance does not make chat backtests free, and vice versa.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real value beyond them: topup_url is minted per call and legitimately differs between reads, balance must be relayed verbatim, and an unreadable balance must be reported as such. However, the per-call-varying URL sits awkwardly against idempotentHint=true and the description does not reconcile the two, leaving a mild inconsistency an agent may trip on.

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 and triggers, and nearly every sentence carries usable content, including the return-key enumeration that substitutes for a missing output schema. It is still long for a zero-argument tool, and the mid-paragraph all-caps LEAD WITH insertion reads as a later patch rather than a designed structure.

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 must carry return semantics and does: it names every returned key, flags the duplicate backtests_affordable/backtests_affordable_from_wallet pair, explains backtest_pack credit precedence and spendable_now, and covers the read-failure case.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter meaning for the description to add or omit.

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 (show the user's Tradetron wallet balance) plus the ancillary outputs (backtest cost, top-up link). An agent can distinguish this from backtest-run tools or plan-limit tools without opening anything else.

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?

Enumerates the triggering conditions: user asks about balance, asks what a backtest costs, says they are out of funds, or asks how to add funds, including the concrete post-refusal case. It also draws an explicit boundary against the subscription plan's backtest_allowed limit, which is the most likely confusion.

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