Carbon Copy MCP Server

Official

by usehoplite

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Pause Trader

pause_trader

Idempotent

Pause copy-trading for a specific trader without unfollowing them. Temporarily stop mirroring their positions on Polymarket.

Instructions

Pause copy-trading for a specific trader without unfollowing them.

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": {
      "wallet": "<wallet>"
    },
    "name": "pause_trader"
  }
}

Input Schema

Name	Required	Description	Default
`wallet`	Yes	The Polymarket wallet address of the trader to pause.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Aug 10, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare this as a mutating (readOnlyHint=false) and idempotent operation. The description adds one useful behavioral nuance—that the follow relationship remains intact—but does not disclose other potential side effects or reversibility. This is adequate but not rich, aligning with the baseline for annotated tools.

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 a single sentence that is front-loaded with the action and contains no extraneous information. It is as concise as possible while still conveying the essential distinction from unfollowing.

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

Completeness4/5

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

For a simple one-parameter mutation tool with idempotent annotation, the description covers the core behavior (pausing copy-trading without unfollowing). It does not mention return values or how to undo via resume_trader, but these are not essential for such a straightforward operation, making it sufficiently complete.

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?

The input schema has 100% coverage for the single 'wallet' parameter, so the schema already explains its meaning. The description does not add any additional parameter-level detail, meriting the baseline score of 3.

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?

The description uses a specific verb ('pause') and a clear resource ('copy-trading for a specific trader'), and explicitly states 'without unfollowing them,' which distinguishes it from siblings like unfollow_trader and resume_trader. This is a precise and unambiguous purpose.

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

Usage Guidelines4/5

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

The description implicitly indicates when to use this tool (to temporarily pause copy-trading) and contrasts it with unfollowing, giving a clear alternative. However, it does not explicitly state when not to use it or provide other exclusions, so it falls short of a full 5.

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