Algo Trader Tools

Add a follower

add_follower

Attaches one of your accounts to the copier with its own rules; leave a rule out for its default. Copying starts at once (unless is_active is false), with what the master opens from then on. Retrying is safe: a second attempt fails with already_following.

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": {
      "copier_id": "<copier_id>",
      "account_id": "<account_id>"
    },
    "name": "add_follower"
  }
}

Input Schema

Name	Required	Description	Default
`max_lot`	No	The most lots one copy may have; null for no limit.
`reverse`	No	Sell when the master buys and the other way round; stop loss and take profit swap.
`symbols`	No	The master's symbol names for `symbol_filter`, which needs at least one unless it is `all`. `XAUUSD` also covers decorated names such as `XAUUSD.m`.
`lot_mode`	No	How each copy is sized. `multiplier`: the master's lots times `lot_value`. `fixed`: `lot_value` lots on every copy. `balance_ratio` / `equity_ratio`: the master's lots scaled by this account's balance or equity against the master's, times `lot_value`. `risk_percent`: sized so the master's stop loss risks `lot_value` percent of this account's equity; trades without a stop loss are skipped.	multiplier
`sessions`	No	When new trades are copied; empty means any time. Closes and changes to copies already open are always copied.
`timezone`	No	The clock `sessions` are read on: `broker` (the master broker's server time, as its MetaTrader charts show it) or a time zone name such as `Europe/London`.	broker
`copier_id`	Yes	The copier's ID.
`is_active`	No	Start paused with `false`.
`lot_value`	No	The multiplier, the lot size or the risk percentage, by `lot_mode`. Above 0 and up to 1000; up to 100 for `risk_percent`. Up to four decimal places.
`account_id`	Yes	One of your connected accounts: connected with its master password, not this copier's master, not a master anywhere and not already copying this master.
`copy_stops`	No	Copy stop loss and take profit, including later changes.
`symbol_map`	No	Master symbol to follower symbol, for names that don't match by themselves. Matching tries this map, then the same name, the name without the broker's decorations (`EURUSD.m`, `US30.cash`), then known aliases (`XAUUSD` and `GOLD`); anything still ambiguous is skipped, never guessed.
`copy_pending`	No	Place the master's pending orders on the follower as pending orders, and follow their changes, rather than copying them once they fill. Needs both terminals on the current version.
`below_minimum`	No	When a copy comes out below the broker's minimum lot: trade the minimum, or skip it.	minimum
`copy_existing`	No	Also copy the positions and pending orders the master already has when the follower is attached. Nothing the master opens or places during a pause is ever copied.
`symbol_filter`	No	`all` copies every symbol, `include` only those in `symbols`, `exclude` all but them.	all
`max_delay_seconds`	No	How late a master trade may still be copied, for example after a reconnect; older ones are skipped.
`max_slippage_pips`	No	The slippage allowed per order; null uses the broker's default.
`adjust_contract_size`	No	Even out different contract sizes between the brokers (gold can be 100 oz a lot at one broker and 10 oz at another). Applies to `multiplier` and the ratio modes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With annotations only saying non-read-only and non-destructive, the description adds real behavioral detail: the attachment takes effect immediately and copies only what the master opens from then on, a paused variant exists via is_active, and a duplicate attempt fails with the specific error `already_following`. That reconciles with idempotentHint=false and tells the agent the failure mode is safe rather than corrupting. It still omits whether there is a cap on followers or what other error codes surface.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and effect, then the immediate-start caveat, then the retry contract. Nothing is repeated from the schema and no sentence could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter, nested-object, side-effecting tool with no output schema and no annotations covering side effects, the description is quite lean; it never mentions what is returned on success or the eligibility constraints on account_id. The 100% schema coverage compensates for most parameter gaps, so it is minimum-viable rather than inadequate.

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%, so the schema already carries the per-parameter meaning and the description correctly leaves it alone. The only added semantics is "leave a rule out for its default," which restates the schema's declared defaults rather than extending them. Baseline 3 is appropriate here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Attaches one of your accounts to the copier with its own rules" names a concrete action and resource, and the phrase "with its own rules" signals that per-follower configuration is supplied inline. It stops short of naming the sibling it supersedes (update_follower) or the inverse (remove_follower), so the agent must infer the split from the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It sets the operational context for when this is used ("copying starts at once") and clarifies the retry situation, but gives no explicit guidance on when to choose this versus update_follower or list_followers, nor any prerequisites about the copier already existing. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Algo Trader Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?