Skip to main content
Glama
Sign In

Algo Trader Tools

by com.algotradertools.mcp
OverviewDiscussionsAdmin

Update a follower

update_follower
DestructiveIdempotent

Change rules, or pause and resume this follower. Changes apply to what's copied from then on.

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>",
      "follower_id": "<follower_id>"
    },
    "name": "update_follower"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_lotNoThe most lots one copy may have; null for no limit.
reverseNoSell when the master buys and the other way round; stop loss and take profit swap.
symbolsNoThe 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_modeNoHow 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.
sessionsNoWhen new trades are copied; empty means any time. Closes and changes to copies already open are always copied.
timezoneNoThe 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`.
copier_idYesThe copier's ID.
is_activeNoPause with `false`. Resuming copies only what the master opens from then on, also with `copy_existing`.
lot_valueNoThe 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.
copy_stopsNoCopy stop loss and take profit, including later changes.
symbol_mapNoMaster 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.
follower_idYesThe follower's ID (not its account's).
copy_pendingNoPlace 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_minimumNoWhen a copy comes out below the broker's minimum lot: trade the minimum, or skip it.
copy_existingNoAlso 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_filterNo`all` copies every symbol, `include` only those in `symbols`, `exclude` all but them.
max_delay_secondsNoHow late a master trade may still be copied, for example after a reconnect; older ones are skipped.
max_slippage_pipsNoThe slippage allowed per order; null uses the broker's default.
adjust_contract_sizeNoEven 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.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare that this is a non-read-only, destructive, idempotent mutation. The description adds meaningful behavioral context beyond the annotations by clarifying that changes affect only what is copied from that point onward, so existing copies are not retroactively rewritten. It still does not spell out partial-update semantics for omitted fields.

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?

The description is two short sentences, front-loads the action, and contains no redundant or filler wording. Every clause contributes to understanding the operation or its temporal effect.

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 destructive update tool, the short description is supplemented heavily by annotations and rich schema descriptions. However, it does not explicitly state the partial-update contract—whether omitted fields stay unchanged—which is important for confidently invoking this tool.

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 the parameter descriptions are unusually detailed, including enum meanings, limits, and nested session behavior. The tool description itself adds no parameter-level meaning, so the schema is doing effectively all of that work.

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?

The description states a specific verb and resource: change rules, or pause/resume 'this follower'. It is clearly distinct from add_follower, remove_follower, and update_copier by naming the follower as the target, though it does not explicitly compare against those siblings.

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?

The phrase 'Change rules, or pause and resume this follower' implies when to use the tool, but there is no explicit when-not guidance, prerequisites, or named alternative for related operations. Usage is inferable from the purpose rather than stated as guidance.

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 toolsInspect
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