Skip to main content
Glama
GemachDAO

GDEX Trading

by GemachDAO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_copy_trade

Destructive

Set up automated copy trading on Solana to mirror a trader's buys and optional sells, using fixed or percentage amounts with stop-loss and take-profit rules.

Instructions

Create a new copy trade to auto-mirror a Solana trader's buys/sells. Solana only.

Input Schema

NameRequiredDescriptionDefault
apiKeyNoAPI key for AES encryption
userIdNoControl wallet address
buyModeYes1 = fixed SOL amount, 2 = percentage of trader amount
chainIdYesMust be 622112261 (Solana)
copySellNoAlso copy sell trades
accountRefNoConnected account from gdex_connect. Supplies session key, wallet address, API key and session data so no secret is passed in chat
lossPercentYesStop-loss percentage (> 0, < 100)
traderWalletYesSolana wallet address of trader to copy
copyBuyAmountYesSOL amount (mode 1) or percentage 0-100 (mode 2)
copyTradeNameYesHuman-readable label
profitPercentYesTake-profit percentage (> 0)
sessionPrivateKeyNoSession private key from sign-in
excludedDexNumbersNoDEX numbers to exclude
isBuyExistingTokenNoBuy tokens already held by trader

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.12.0
    • addedInput schema / properties / accountRef
      Added value: +{
+  "description": "Connected account from gdex_connect. Supplies session key, wallet address, API key and session data so no secret is passed in chat",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "apiKey",
-  "userId",
-  "sessionPrivateKey",
-  "traderWallet",
-  "copyTradeName",
-  "chainId",
-  "buyMode",
-  "copyBuyAmount",
-  "lossPercent",
-  "profitPercent"
-]New value: +[
+  "traderWallet",
+  "copyTradeName",
+  "chainId",
+  "buyMode",
+  "copyBuyAmount",
+  "lossPercent",
+  "profitPercent"
+]
  2. First observedv4.11.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is covered. The description adds the meaningful behavioral fact that this sets up continuous auto-mirroring of another trader's buys/sells, but it never discloses that real funds are committed, that loss/profit thresholds stop the mirroring, or that an authenticated account is required.

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?

Two short sentences, the core action front-loaded and the platform constraint immediately after. Nothing is wasted or buried.

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?

This is a destructive, open-world mutation with 14 parameters (7 required) and no output schema; the description is far too thin for that weight. It omits the authentication path (accountRef/gdex_connect), the implication that live trading starts immediately, and any mention of how the required risk parameters govern behavior.

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%, so all 14 parameters are documented in the schema itself. The description adds no extra meaning about buy modes, stop-loss/take-profit interaction, or how accountRef replaces raw secrets, so the baseline 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 states a specific verb and resource ('Create a new copy trade') plus its effect ('auto-mirror a Solana trader's buys/sells'), and the 'Solana only' clause implicitly separates it from the sibling create_hl_copy_trade. It's clear, though the sibling differentiation is by inference rather than by naming the alternative.

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 'Solana only' constraint tells the agent when this tool applies versus the HL equivalents, but there is no explicit guidance on prerequisites (gdex_connect/accountRef, chainId 622112261), no named alternatives, and no when-not-to-use conditions. Usage is implied rather than stated.

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