Skip to main content
Glama

Get Upgrade URL

get_upgrade_url
Read-only

Get a Stripe checkout URL to upgrade the user's TraderWAI plan. Plans: FREE (1 broker account, 5 executions/day, 1 new conditional order/day, 2-week backtests); PLUS (3 accounts, 25 executions/day, auto-execution, 5 new conditional orders/day, 6-month backtests, no MetaTrader); TRADER (5 accounts, 100 executions/day, auto-execution, 10 conditional orders, MetaTrader, 1-year backtests); MAX (10 accounts, unlimited executions, unlimited conditional orders, full risk limits, MetaTrader, all history). MetaTrader is a premium broker: only on Trader and Max, where any of the plan's accounts can be MetaTrader. No free trials: the first month of any monthly plan is 50% off for a first subscription. Monthly and yearly billing (yearly is cheaper). Returns a URL the user must open to pay, with the price and any discount. If the user already pays, the result has changePlan=true: it is a prorated change of the same subscription (unused days of the current plan are credited; preview.amountDue is charged today, or nothing during a trial) and url is the pricing page where the user confirms it. Downgrades are done by the user on the pricing page.

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": {
      "plan": "<plan>"
    },
    "name": "get_upgrade_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesThe target plan to upgrade to (PLUS only when it is on sale: the plan-limit messages say which plan to offer)
intervalNoBilling period (default month)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it explains that the tool returns a URL the user must open to pay, includes price and discount, and for existing subscribers returns changePlan=true with a prorated charge based on preview.amountDue. It also discloses that downgrades are not handled here.

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?

Purpose is front-loaded, followed by plan details and billing behavior. The plan catalog is dense and could be more scannable, but every section is relevant to selecting a plan or understanding the returned URL.

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?

There is no output schema, so the description carries return-value semantics, and it explains the URL, price, discount, changePlan flag, and prorated charge behavior. For a read-only URL-generation tool, this is complete enough to call correctly.

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 100%, so the schema already documents both parameters and enums. The description adds useful meaning by comparing plan limits, explaining MetaTrader availability, and noting that yearly billing is cheaper, which helps the agent choose the plan and interval.

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 the specific verb and result: get a Stripe checkout URL to upgrade the user's TraderWAI plan. It also distinguishes the upgrade path from downgrades by noting downgrades happen on the pricing page.

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?

The use case is clear from the description, and it gives relevant conditions: PLUS only when on sale, and downgrades are self-service rather than via this tool. It does not explicitly frame when to call it versus alternatives, though no upgrade sibling is present in the provided list.

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