Skip to main content
Glama
Sign In
Carbon Copy MCP Server

Carbon Copy MCP Server

Official
by usehoplite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Trader Performance

get_trader_performance
Read-only

Retrieve performance metrics and trading history for a Polymarket trader using their wallet address, enabling analysis of copy-trading candidates.

Instructions

Retrieve performance metrics and history for a trader.

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

Input Schema

NameRequiredDescriptionDefault
walletYesThe Polymarket wallet address of the trader.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.3/5.0
Behavior2/5

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

The annotation readOnlyHint=true already communicates that this is a safe read operation, so the description does not need to restate that. The description adds minimal behavioral context beyond the tool's name—'performance metrics and history' is vague and does not clarify what specific data is returned, whether it is aggregated, or if it includes time-series details.

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, front-loaded sentence with no unnecessary words. It directly states the action and target, earning a perfect conciseness score.

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?

The tool is simple with one parameter and a read-only annotation, but the description lacks specificity about the output structure or the exact metrics included. Without an output schema, an agent would not know whether the result is a single object or a time series, leaving a moderate gap in completeness.

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 parameter 'wallet', with a clear description of 'The Polymarket wallet address of the trader.' The tool description adds no additional parameter information, so the baseline score of 3 applies.

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 uses the specific verb 'Retrieve' and identifies the resource as 'performance metrics and history' for a trader, clearly stating the tool's function. However, it does not distinguish this from closely related siblings like get_pnl_by_trader or get_pnl_history, which also deal with trader performance metrics.

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 description implies usage by stating it retrieves performance metrics and history, but it provides no explicit guidance on when to use this tool over alternatives. With siblings like get_pnl_by_trader and get_portfolio_history, the absence of exclusionary or comparative notes leaves the choice ambiguous.

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

Deploy Server

Other Tools