Algo Trader Tools

Remove a follower

remove_follower

DestructiveIdempotent

Detaches the account from the copier and deletes its activity log. The account stays connected. With close_positions=true its copies are closed first.

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": "remove_follower"
  }
}

Input Schema

Name	Required	Description
`copier_id`	Yes	The copier's ID.
`follower_id`	Yes	The follower's ID (not its account's).
`close_positions`	No	`true` pauses copying and closes every copy at market before deleting; if a terminal refuses, nothing is deleted (`close_failed`). `false` leaves the copies open on the followers as ordinary positions.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds genuinely new context: the activity log is permanently deleted, the account itself stays connected, and positions are left open as ordinary positions unless close_positions is set. It does not state required permissions or whether the removal can be undone, which is a notable gap for a destructive mutation.

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?

Three short sentences with the main effect front-loaded and the flag behavior last; nothing is wasted. Minor cost is the ambiguous 'the account' reference, which requires the reader to infer 'the follower'.

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 small, fully-documented three-parameter mutation with no output schema, the description covers the key destructive side effects adequately. However, it leaves out reversibility, required permissions, and how it differs from the closely related disconnect_account and update_follower tools, which an agent needs before choosing it.

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 all three parameters are fully documented, including the close_failed terminal-refusal behavior. The description merely restates the close_positions effect ('its copies are closed first'), adding no syntax or constraint detail beyond the schema.

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?

States a specific verb and resource chain: detaching a follower account from a copier and deleting its activity log, plus the effect of close_positions. It is clear what the tool does, but the phrasing 'the account' rather than 'the follower' is imprecise given the sibling terminologies (disconnect_account, update_follower), and it never differentiates itself from 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 Guidelines2/5

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

No guidance on when to use this versus add_follower, disconnect_account, or update_follower. The only conditional statement concerns the close_positions flag, which is invocation mechanics rather than selection 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 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?