Carbon Copy MCP Server

Official

by usehoplite

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Batch Update Traders

batch_update_traders

Idempotent

Batch update copy trading settings for multiple followed traders in one request. Streamline configuration by applying changes across traders efficiently.

Instructions

Update settings across multiple followed traders in one request.

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": {
      "updates": "<updates>"
    },
    "name": "batch_update_traders"
  }
}

Input Schema

Name	Required	Description	Default
`updates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Aug 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true. Description adds no behavioral context about partial failures, atomicity, or permission requirements beyond the redundant 'update' wording.

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?

One sentence of 11 words, front-loaded with the verb 'Update', and contains no filler or redundant information.

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

Completeness2/5

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

Batch operation with a nested array parameter and no output schema. Description gives no information about response format, error handling, or partial update behavior, making it inadequate for an agent to fully understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not compensate. Field names like maxCopyAmount and copyPercentage are self-explanatory only at a surface level; no meaning or usage guidance is provided for these parameters.

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?

Description uses specific verb 'update', identifies resource 'settings across multiple followed traders', and specifies batch nature with 'in one request'. This clearly distinguishes it from sibling tool update_trader which handles a single trader.

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?

Implies batch usage via 'multiple followed traders' but does not explicitly state when to prefer this over update_trader or provide exclusions. Usage context is inferred rather than stated.

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