Skip to main content
Glama

Preflight copy-trading a wallet

preflight_copy
Read-onlyIdempotent

COPY / WATCH / VETO verdict for copy-trading a Polymarket wallet, with the numbers behind it (fee-inclusive copier ROI from a fixed $5-entry / +2c-slippage simulation, win rate, entry-price buckets, category mix). Wallets not yet computed return QUEUED free of charge - typically ready in minutes (retry_after_seconds tells you when); worst case about an hour. Price: $0.10 per call via x402 or 5 credits with a bearer token; sandbox: true is free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "preflight_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletNoPolymarket wallet address (0x + 40 hex). Required for live calls; optional with sandbox: true.
sandboxNotrue = free deterministic example response, never charged.

Output Schema

NameRequiredDescriptionDefault
okYes
nameNoLast pseudonym seen on the tape.
noteNo
paidNoPayment record. Per-call x402 lane: price_paid_usdc / transaction / network / receipt. Credit lane: credits_used / credits_remaining. Absent on sandbox and free QUEUED responses.
methodNo
walletNo
windowNo
reasonsNo
sandboxNoTrue when the response is the free deterministic sandbox example.
verdictYesCOPY only for out-of-sample-validated wallets; in-sample verdicts are capped at WATCH. VETO = negative fee-inclusive copier ROI or both-sides farming. NO_COVERAGE = below the 10-first-entry floor. QUEUED = not computed yet (free) - typically ready in minutes (retry_after_seconds tells you when); worst case about an hour.
n_pendingNo
n_resolvedNo
active_daysNo
computed_atNo
win_rate_pctNo
last_trade_atNo
both_sides_pctNoShare of markets where the wallet bought BOTH outcomes (farming smell).
first_trade_atNo
avg_entry_priceNo
n_first_entriesNoDistinct (market, outcome) first BUY entries in the window; crypto up/down markets excluded.
category_mix_pctNo
clips_per_entry_avgNoIceberg signal - how many fills the wallet splits one entry into.
entry_price_bucketsNo
retry_after_secondsNoQUEUED only.
roi_fee_inclusive_pctNoSlippage basis minus explicit 2026 taker fees (rate*p*(1-p)).
roi_slippage_basis_pctNo$5/entry at whale price +2c slippage, held to resolution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / verdict / description
      Previous value: -"COPY only for out-of-sample-validated wallets; in-sample verdicts are capped at WATCH. VETO = negative fee-inclusive copier ROI or both-sides farming. NO_COVERAGE = below the 10-first-entry floor. QUEUED = not computed yet, retry in ~1h (free)."New value: +"COPY only for out-of-sample-validated wallets; in-sample verdicts are capped at WATCH. VETO = negative fee-inclusive copier ROI or both-sides farming. NO_COVERAGE = below the 10-first-entry floor. QUEUED = not computed yet (free) - typically ready in minutes (retry_after_seconds tells you when); worst case about an hour."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds that results can be QUEUED with retry_after_seconds, worst-case 1 hour, and pricing details. No contradiction.

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?

Three sentences, each packed with essential information: verdict content, queuing behavior, pricing. Front-loaded with key verb/resource. No fluff.

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

Completeness5/5

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

Given the tool's complexity, the description covers return values (verdict details), queuing, pricing, and sandbox. Output schema exists, so return format is documented. Complete.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for wallet and sandbox. Description reinforces that wallet is optional with sandbox and sandbox is free, adding value beyond schema.

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?

Clearly states it returns a COPY/WATCH/VETO verdict for copy-trading a Polymarket wallet, with specific metrics (ROI, win rate, etc.). Distinguishes from sibling preflight_trade by focusing on copy-trading.

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?

Explains when to use (get copy-trading verdict), includes queuing behavior and retry timing, and notes pricing. Does not explicitly list exclusions but context is sufficient.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources