Skip to main content
Glama

Create Broker Account

create_broker_account

Connect a new broker account to TraderWAI (TradeLocker, Match-Trader, MetaTrader, DXtrade, Capital.com, Binance spot or Bybit USDT perpetuals). MetaTrader is a premium broker, only on the Trader and Max plans, where any of the plan's accounts can be MetaTrader (Trader 5 accounts, Max 10). Switching to another MetaTrader account is free and unlimited: delete the old one and add the new one, or change the account number with update_broker_account. Confirm the account number, master password and server with the user before adding it. For cTrader accounts, use the connect_ctrader tool instead (it uses OAuth). tastytrade (US futures, beta) cannot be added with this tool either: it is connected with the tastytrade login (OAuth) from the TraderWAI website (Settings → Broker accounts → Connect tastytrade); send the user there. The credentials are encrypted at rest and used only to authenticate with the broker for trade execution. After creating, use test_broker_account to verify the connection works. Available on all plans (FREE: 1, PLUS: 3, TRADER: 5, MAX: 10).

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": {
      "label": "<label>",
      "environment": "<environment>",
      "email": "<email>",
      "password": "<password>"
    },
    "name": "create_broker_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesBroker login email. MetaTrader: the account number (login). DXtrade: the platform username. Capital.com / Binance / Bybit / Toobit / Kraken: the API key. eToro: the public API key.
labelYesFriendly name for this account (e.g. "My Demo Account")
serverNoNot used for Binance, Bybit, Toobit, Kraken or eToro. Capital.com: the email the user logs in to Capital.com with. TradeLocker: the broker server name (e.g. "HEROFX"). Match-Trader: the URL of the broker's Match-Trader platform (e.g. "https://mtr.e8markets.com"; any page of it works). MetaTrader: the server name exactly as in MetaTrader (e.g. "HeroFX-Trade"). DXtrade: the web address of the broker's DXtrade platform (e.g. "https://trader.blueberrymarkets.com"), plus "#<domain>" only if the broker uses a domain other than "default".
passwordYesBroker login password. MetaTrader: the master password (the investor password only allows reading). Binance: the API secret (or the Ed25519 private key in PEM). Bybit / Toobit: the API secret. Kraken: the private key of the API key. eToro: the user key created for that environment (Demo or Real) with Trading write permission. Capital.com: the custom password chosen when generating the API key (not the Capital.com password).
brokerTypeNoPlatform: "tradelocker" (default), "matchtrader", "metatrader", "dxtrade" (username + password + platform address; the broker must enable API access; beta), "capitalcom" (Capital.com's own platform; API key + its password + login email; the user enables two-factor authentication and generates the key in Capital.com → Settings → API integrations; environment "demo" = Capital.com demo account), "binance" (spot; environment "demo" = Binance Spot Testnet) "bybit" (USDT perpetuals; environment "demo" = Bybit Demo Trading), "etoro" (beta; public API key + user key from eToro → Settings → Trading → API Key Management; the user key is for one environment, Demo = virtual portfolio, and needs Trading «Write»; what can be traded depends on the eToro account: with CFDs blocked only buying stocks and crypto works; suggest connecting it from the web), "toobit" (USDT perpetuals, beta; environment must be "live": Toobit has no demo in its API) or "kraken" (spot, beta; environment must be "live": Kraken has no demo; API key with «Query funds», query open/closed orders, «Create & modify orders» and «Cancel & close orders», never withdrawals). For Toobit the API key needs read and write access to «Contract» (futures) only, never withdrawals, ideally restricted to IP 187.7.69.7. For Bybit the API key needs only «Contract → Orders & Positions» (never withdrawals), ideally restricted to IP 187.7.69.7. For Binance the user creates an API key with only «Spot & Margin trading» enabled (never withdrawals), ideally restricted to IP 187.7.69.7; suggest connecting it from the web (Settings → Broker accounts) rather than pasting the secret in the chat. For cTrader use the connect_ctrader tool. MetaTrader setup takes 1-3 minutes (check metaapiState with get_broker_accounts); Trader includes 1 MetaTrader account, Max 3.
mtPlatformNoMetaTrader only: "mt5" (default) or "mt4"
environmentYes"demo" for paper trading, "live" for real money
subAccountIdNoOptional, TradeLocker: which account of the login to use, by its id or accNum (test_broker_account lists them). One login can hold several accounts (e.g. accNum 1 and 4); without this the first one is used. To run separate strategies, create one connection per account with the same login and a different subAccountId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / brokerType / description
      Previous value: -"Platform: \"tradelocker\" (default), \"matchtrader\", \"metatrader\", \"dxtrade\" (username + password + platform address; the broker must enable API access; beta), \"capitalcom\" (Capital.com's own platform; API key + its password + login email; the user enables two-factor authentication and generates the key in Capital.com → Settings → API integrations; environment \"demo\" = Capital.com demo account; beta), \"binance\" (spot; environment \"demo\" = Binance Spot Testnet) \"bybit\" (USDT perpetuals; environment \"demo\" = Bybit Demo Trading), \"etoro\" (beta; public API key + user key from eToro → Settings → Trading → API Key Management; the user key is for one environment, Demo = virtual portfolio, and needs Trading «Write»; what can be traded depends on the eToro account: with CFDs blocked only buying stocks and crypto works; suggest connecting it from the web) or \"toobit\" (USDT perpetuals, beta; environment must be \"live\": Toobit has no demo in its API). For Toobit the API key needs read and write access to «Contract» (futures) only, never withdrawals, ideally restricted to IP 187.7.69.7. For Bybit the API key needs only «Contract → Orders & Positions» (never withdrawals), ideally restricted to IP 187.7.69.7. For Binance the user creates an API key with only «Spot & Margin trading» enabled (never withdrawals), ideally restricted to IP 187.7.69.7; suggest connecting it from the web (Settings → Broker accounts) rather than pasting the secret in the chat. For cTrader use the connect_ctrader tool. MetaTrader setup takes 1-3 minutes (check metaapiState with get_broker_accounts); Trader includes 1 MetaTrader account, Max 3."New value: +"Platform: \"tradelocker\" (default), \"matchtrader\", \"metatrader\", \"dxtrade\" (username + password + platform address; the broker must enable API access; beta), \"capitalcom\" (Capital.com's own platform; API key + its password + login email; the user enables two-factor authentication and generates the key in Capital.com → Settings → API integrations; environment \"demo\" = Capital.com demo account), \"binance\" (spot; environment \"demo\" = Binance Spot Testnet) \"bybit\" (USDT perpetuals; environment \"demo\" = Bybit Demo Trading), \"etoro\" (beta; public API key + user key from eToro → Settings → Trading → API Key Management; the user key is for one environment, Demo = virtual portfolio, and needs Trading «Write»; what can be traded depends on the eToro account: with CFDs blocked only buying stocks and crypto works; suggest connecting it from the web), \"toobit\" (USDT perpetuals, beta; environment must be \"live\": Toobit has no demo in its API) or \"kraken\" (spot, beta; environment must be \"live\": Kraken has no demo; API key with «Query funds», query open/closed orders, «Create & modify orders» and «Cancel & close orders», never withdrawals). For Toobit the API key needs read and write access to «Contract» (futures) only, never withdrawals, ideally restricted to IP 187.7.69.7. For Bybit the API key needs only «Contract → Orders & Positions» (never withdrawals), ideally restricted to IP 187.7.69.7. For Binance the user creates an API key with only «Spot & Margin trading» enabled (never withdrawals), ideally restricted to IP 187.7.69.7; suggest connecting it from the web (Settings → Broker accounts) rather than pasting the secret in the chat. For cTrader use the connect_ctrader tool. MetaTrader setup takes 1-3 minutes (check metaapiState with get_broker_accounts); Trader includes 1 MetaTrader account, Max 3."
    • changedInput schema / properties / brokerType / enum
      Previous value: -[
      -  "tradelocker",
      -  "matchtrader",
      -  "metatrader",
      -  "dxtrade",
      -  "capitalcom",
      -  "etoro",
      -  "binance",
      -  "bybit",
      -  "toobit"
      -]New value: +[
      +  "tradelocker",
      +  "matchtrader",
      +  "metatrader",
      +  "dxtrade",
      +  "capitalcom",
      +  "etoro",
      +  "binance",
      +  "bybit",
      +  "toobit",
      +  "kraken"
      +]
    • changedInput schema / properties / email / description
      Previous value: -"Broker login email. MetaTrader: the account number (login). DXtrade: the platform username. Capital.com / Binance / Bybit / Toobit: the API key. eToro: the public API key."New value: +"Broker login email. MetaTrader: the account number (login). DXtrade: the platform username. Capital.com / Binance / Bybit / Toobit / Kraken: the API key. eToro: the public API key."
    • changedInput schema / properties / password / description
      Previous value: -"Broker login password. MetaTrader: the master password (the investor password only allows reading). Binance: the API secret (or the Ed25519 private key in PEM). Bybit / Toobit: the API secret. eToro: the user key created for that environment (Demo or Real) with Trading write permission. Capital.com: the custom password chosen when generating the API key (not the Capital.com password)."New value: +"Broker login password. MetaTrader: the master password (the investor password only allows reading). Binance: the API secret (or the Ed25519 private key in PEM). Bybit / Toobit: the API secret. Kraken: the private key of the API key. eToro: the user key created for that environment (Demo or Real) with Trading write permission. Capital.com: the custom password chosen when generating the API key (not the Capital.com password)."
    • changedInput schema / properties / server / description
      Previous value: -"Not used for Binance, Bybit, Toobit or eToro. Capital.com: the email the user logs in to Capital.com with. TradeLocker: the broker server name (e.g. \"HEROFX\"). Match-Trader: the URL of the broker's Match-Trader platform (e.g. \"https://mtr.e8markets.com\"; any page of it works). MetaTrader: the server name exactly as in MetaTrader (e.g. \"HeroFX-Trade\"). DXtrade: the web address of the broker's DXtrade platform (e.g. \"https://trader.blueberrymarkets.com\"), plus \"#<domain>\" only if the broker uses a domain other than \"default\"."New value: +"Not used for Binance, Bybit, Toobit, Kraken or eToro. Capital.com: the email the user logs in to Capital.com with. TradeLocker: the broker server name (e.g. \"HEROFX\"). Match-Trader: the URL of the broker's Match-Trader platform (e.g. \"https://mtr.e8markets.com\"; any page of it works). MetaTrader: the server name exactly as in MetaTrader (e.g. \"HeroFX-Trade\"). DXtrade: the web address of the broker's DXtrade platform (e.g. \"https://trader.blueberrymarkets.com\"), plus \"#<domain>\" only if the broker uses a domain other than \"default\"."
  2. Changed5 schema fields changed
    • changedInput schema / properties / brokerType / description
      Previous value: -"Platform: \"tradelocker\" (default), \"matchtrader\", \"metatrader\", \"dxtrade\" (username + password + platform address; the broker must enable API access; beta), \"capitalcom\" (Capital.com's own platform; API key + its password + login email; the user enables two-factor authentication and generates the key in Capital.com → Settings → API integrations; environment \"demo\" = Capital.com demo account; beta), \"binance\" (spot; environment \"demo\" = Binance Spot Testnet) \"bybit\" (USDT perpetuals; environment \"demo\" = Bybit Demo Trading) or \"toobit\" (USDT perpetuals, beta; environment must be \"live\": Toobit has no demo in its API). For Toobit the API key needs read and write access to «Contract» (futures) only, never withdrawals, ideally restricted to IP 187.7.69.7. For Bybit the API key needs only «Contract → Orders & Positions» (never withdrawals), ideally restricted to IP 187.7.69.7. For Binance the user creates an API key with only «Spot & Margin trading» enabled (never withdrawals), ideally restricted to IP 187.7.69.7; suggest connecting it from the web (Settings → Broker accounts) rather than pasting the secret in the chat. For cTrader use the connect_ctrader tool. MetaTrader setup takes 1-3 minutes (check metaapiState with get_broker_accounts); Trader includes 1 MetaTrader account, Max 3."New value: +"Platform: \"tradelocker\" (default), \"matchtrader\", \"metatrader\", \"dxtrade\" (username + password + platform address; the broker must enable API access; beta), \"capitalcom\" (Capital.com's own platform; API key + its password + login email; the user enables two-factor authentication and generates the key in Capital.com → Settings → API integrations; environment \"demo\" = Capital.com demo account; beta), \"binance\" (spot; environment \"demo\" = Binance Spot Testnet) \"bybit\" (USDT perpetuals; environment \"demo\" = Bybit Demo Trading), \"etoro\" (beta; public API key + user key from eToro → Settings → Trading → API Key Management; the user key is for one environment, Demo = virtual portfolio, and needs Trading «Write»; what can be traded depends on the eToro account: with CFDs blocked only buying stocks and crypto works; suggest connecting it from the web) or \"toobit\" (USDT perpetuals, beta; environment must be \"live\": Toobit has no demo in its API). For Toobit the API key needs read and write access to «Contract» (futures) only, never withdrawals, ideally restricted to IP 187.7.69.7. For Bybit the API key needs only «Contract → Orders & Positions» (never withdrawals), ideally restricted to IP 187.7.69.7. For Binance the user creates an API key with only «Spot & Margin trading» enabled (never withdrawals), ideally restricted to IP 187.7.69.7; suggest connecting it from the web (Settings → Broker accounts) rather than pasting the secret in the chat. For cTrader use the connect_ctrader tool. MetaTrader setup takes 1-3 minutes (check metaapiState with get_broker_accounts); Trader includes 1 MetaTrader account, Max 3."
    • changedInput schema / properties / brokerType / enum
      Previous value: -[
      -  "tradelocker",
      -  "matchtrader",
      -  "metatrader",
      -  "dxtrade",
      -  "capitalcom",
      -  "binance",
      -  "bybit",
      -  "toobit"
      -]New value: +[
      +  "tradelocker",
      +  "matchtrader",
      +  "metatrader",
      +  "dxtrade",
      +  "capitalcom",
      +  "etoro",
      +  "binance",
      +  "bybit",
      +  "toobit"
      +]
    • changedInput schema / properties / email / description
      Previous value: -"Broker login email. MetaTrader: the account number (login). DXtrade: the platform username. Capital.com / Binance / Bybit / Toobit: the API key."New value: +"Broker login email. MetaTrader: the account number (login). DXtrade: the platform username. Capital.com / Binance / Bybit / Toobit: the API key. eToro: the public API key."
    • changedInput schema / properties / password / description
      Previous value: -"Broker login password. MetaTrader: the master password (the investor password only allows reading). Binance: the API secret (or the Ed25519 private key in PEM). Bybit / Toobit: the API secret. Capital.com: the custom password chosen when generating the API key (not the Capital.com password)."New value: +"Broker login password. MetaTrader: the master password (the investor password only allows reading). Binance: the API secret (or the Ed25519 private key in PEM). Bybit / Toobit: the API secret. eToro: the user key created for that environment (Demo or Real) with Trading write permission. Capital.com: the custom password chosen when generating the API key (not the Capital.com password)."
    • changedInput schema / properties / server / description
      Previous value: -"Not used for Binance, Bybit or Toobit. Capital.com: the email the user logs in to Capital.com with. TradeLocker: the broker server name (e.g. \"HEROFX\"). Match-Trader: the URL of the broker's Match-Trader platform (e.g. \"https://mtr.e8markets.com\"; any page of it works). MetaTrader: the server name exactly as in MetaTrader (e.g. \"HeroFX-Trade\"). DXtrade: the web address of the broker's DXtrade platform (e.g. \"https://trader.blueberrymarkets.com\"), plus \"#<domain>\" only if the broker uses a domain other than \"default\"."New value: +"Not used for Binance, Bybit, Toobit or eToro. Capital.com: the email the user logs in to Capital.com with. TradeLocker: the broker server name (e.g. \"HEROFX\"). Match-Trader: the URL of the broker's Match-Trader platform (e.g. \"https://mtr.e8markets.com\"; any page of it works). MetaTrader: the server name exactly as in MetaTrader (e.g. \"HeroFX-Trade\"). DXtrade: the web address of the broker's DXtrade platform (e.g. \"https://trader.blueberrymarkets.com\"), plus \"#<domain>\" only if the broker uses a domain other than \"default\"."
  3. Changed5 schema fields changed
    • changedInput schema / properties / brokerType / description
      Previous value: -"Platform: \"tradelocker\" (default), \"matchtrader\", \"metatrader\", \"dxtrade\" (username + password + platform address; the broker must enable API access; beta), \"capitalcom\" (Capital.com's own platform; API key + its password + login email; the user enables two-factor authentication and generates the key in Capital.com → Settings → API integrations; environment \"demo\" = Capital.com demo account; beta), \"binance\" (spot; environment \"demo\" = Binance Spot Testnet) or \"bybit\" (USDT perpetuals; environment \"demo\" = Bybit Demo Trading). For Bybit the API key needs only «Contract → Orders & Positions» (never withdrawals), ideally restricted to IP 187.7.69.7. For Binance the user creates an API key with only «Spot & Margin trading» enabled (never withdrawals), ideally restricted to IP 187.7.69.7; suggest connecting it from the web (Settings → Broker accounts) rather than pasting the secret in the chat. For cTrader use the connect_ctrader tool. MetaTrader setup takes 1-3 minutes (check metaapiState with get_broker_accounts); Trader includes 1 MetaTrader account, Max 3."New value: +"Platform: \"tradelocker\" (default), \"matchtrader\", \"metatrader\", \"dxtrade\" (username + password + platform address; the broker must enable API access; beta), \"capitalcom\" (Capital.com's own platform; API key + its password + login email; the user enables two-factor authentication and generates the key in Capital.com → Settings → API integrations; environment \"demo\" = Capital.com demo account; beta), \"binance\" (spot; environment \"demo\" = Binance Spot Testnet) \"bybit\" (USDT perpetuals; environment \"demo\" = Bybit Demo Trading) or \"toobit\" (USDT perpetuals, beta; environment must be \"live\": Toobit has no demo in its API). For Toobit the API key needs read and write access to «Contract» (futures) only, never withdrawals, ideally restricted to IP 187.7.69.7. For Bybit the API key needs only «Contract → Orders & Positions» (never withdrawals), ideally restricted to IP 187.7.69.7. For Binance the user creates an API key with only «Spot & Margin trading» enabled (never withdrawals), ideally restricted to IP 187.7.69.7; suggest connecting it from the web (Settings → Broker accounts) rather than pasting the secret in the chat. For cTrader use the connect_ctrader tool. MetaTrader setup takes 1-3 minutes (check metaapiState with get_broker_accounts); Trader includes 1 MetaTrader account, Max 3."
    • changedInput schema / properties / brokerType / enum
      Previous value: -[
      -  "tradelocker",
      -  "matchtrader",
      -  "metatrader",
      -  "dxtrade",
      -  "capitalcom",
      -  "binance",
      -  "bybit"
      -]New value: +[
      +  "tradelocker",
      +  "matchtrader",
      +  "metatrader",
      +  "dxtrade",
      +  "capitalcom",
      +  "binance",
      +  "bybit",
      +  "toobit"
      +]
    • changedInput schema / properties / email / description
      Previous value: -"Broker login email. MetaTrader: the account number (login). DXtrade: the platform username. Capital.com / Binance / Bybit: the API key."New value: +"Broker login email. MetaTrader: the account number (login). DXtrade: the platform username. Capital.com / Binance / Bybit / Toobit: the API key."
    • changedInput schema / properties / password / description
      Previous value: -"Broker login password. MetaTrader: the master password (the investor password only allows reading). Binance: the API secret (or the Ed25519 private key in PEM). Bybit: the API secret. Capital.com: the custom password chosen when generating the API key (not the Capital.com password)."New value: +"Broker login password. MetaTrader: the master password (the investor password only allows reading). Binance: the API secret (or the Ed25519 private key in PEM). Bybit / Toobit: the API secret. Capital.com: the custom password chosen when generating the API key (not the Capital.com password)."
    • changedInput schema / properties / server / description
      Previous value: -"Not used for Binance or Bybit. Capital.com: the email the user logs in to Capital.com with. TradeLocker: the broker server name (e.g. \"HEROFX\"). Match-Trader: the URL of the broker's Match-Trader platform (e.g. \"https://mtr.e8markets.com\"; any page of it works). MetaTrader: the server name exactly as in MetaTrader (e.g. \"HeroFX-Trade\"). DXtrade: the web address of the broker's DXtrade platform (e.g. \"https://trader.blueberrymarkets.com\"), plus \"#<domain>\" only if the broker uses a domain other than \"default\"."New value: +"Not used for Binance, Bybit or Toobit. Capital.com: the email the user logs in to Capital.com with. TradeLocker: the broker server name (e.g. \"HEROFX\"). Match-Trader: the URL of the broker's Match-Trader platform (e.g. \"https://mtr.e8markets.com\"; any page of it works). MetaTrader: the server name exactly as in MetaTrader (e.g. \"HeroFX-Trade\"). DXtrade: the web address of the broker's DXtrade platform (e.g. \"https://trader.blueberrymarkets.com\"), plus \"#<domain>\" only if the broker uses a domain other than \"default\"."
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds substantive context beyond that: credentials are encrypted at rest and used only for broker authentication, MetaTrader provisioning takes 1-3 minutes and is tracked via metaapiState, and plan-tier caps (FREE 1 / PLUS 3 / TRADER 5 / MAX 10). The non-idempotent, external-side-effect nature of the call is made concrete rather than left to the hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the sibling routing are front-loaded and earn their place, but the single dense paragraph repeats material already present in the brokerType, password and email schema descriptions (API key permission scopes, IP whitelist 187.7.69.7, per-broker secret semantics). That duplication bloats the description without adding decision-relevant information.

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 multi-platform, 8-parameter creation tool with no output schema, the description covers everything an agent needs: supported and unsupported platforms, credential handling and security posture, plan limits, verification follow-up, and the exact alternative tools for the excluded cases. Nothing critical 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 100%, so the baseline is 3, but the description adds real meaning: it tells the agent to confirm the account number, master password and server with the user, and explains plan-dependent constraints on MetaTrader accounts that the schema cannot express. It does not walk through individual parameters like subAccountId, which the schema already documents well.

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 and resource ("Connect a new broker account to TraderWAI") and immediately enumerates the supported platforms (TradeLocker, Match-Trader, MetaTrader, DXtrade, Capital.com, Binance, Bybit). It explicitly carves out cTrader and tastytrade as not handled here, so an agent can distinguish this from connect_ctrader without inspecting either schema.

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?

Gives explicit routing rules: use connect_ctrader for cTrader (OAuth), send tastytrade users to the website, and use update_broker_account to change an existing MetaTrader account number. It also states a prerequisite behavior (confirm account number, master password and server with the user) and a follow-up step (test_broker_account), which is exactly the when/when-not guidance an agent needs.

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