Skip to main content
Glama
Sign In
Carbon Copy MCP Server

Carbon Copy MCP Server

Official
by usehoplite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Trader

get_trader
Read-only

Retrieve detailed information about a specific Polymarket trader by providing their wallet address, including performance and activity.

Instructions

Retrieve details about a specific trader you are following.

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

Input Schema

NameRequiredDescriptionDefault
walletYesThe Polymarket wallet address of the trader.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description does not need to cover safety. It adds the constraint that the trader must be one you are following, which is not in the schema or annotations, providing useful behavioral context beyond what structured data offers.

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 front-loads the action and contains zero unnecessary words. It is concise and well structured.

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 get-by-id tool with one parameter and strong annotations, the description is mostly complete. However, it does not specify what 'details' are returned or include any return format, which would be helpful given there is no output schema.

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% for the single 'wallet' parameter, so the schema already explains the parameter. The description adds no extra parameter semantics, making the baseline of 3 appropriate.

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 ('Retrieve') and resource ('details about a specific trader'), and the phrase 'you are following' distinguishes it from list/discover tools. It clearly states what the tool does and is not a tautology.

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 when you need details about a specific trader you follow, but it does not explicitly state when to use this tool versus alternatives like get_trader_performance or list_traders. No exclusions or alternative tool names are mentioned.

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