Skip to main content
Glama
GemachDAO

GDEX Trading

by GemachDAO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_hl_copy_trade

Destructive

Update a Hyperliquid perpetual copy-trade configuration by rewriting all fields from the full payload; optionally toggle active/paused or permanently delete it without closing open positions.

Instructions

Low-level HL perp copy trade update (prefer update_hl_copy_trade_settings / pause_hl_copy_trade / resume_hl_copy_trade / delete_hl_copy_trade). Every field is rewritten from this payload, so pass the full current config. isDelete=true permanently deletes the configuration; perp positions it opened are NOT closed and their TP/SL orders are NOT cancelled. isChangeStatus=true TOGGLES active/paused relative to the stored state. isDelete and isChangeStatus cannot both be true.

Input Schema

NameRequiredDescriptionDefault
apiKeyNoAPI key
userIdNoControl wallet address
copyModeYes1 = fixed USD per order, 2 = proportion
isDeleteNoPermanently delete the configuration (positions stay open)
accountRefNoConnected account from gdex_connect. Supplies session key, wallet address, API key and session data so no secret is passed in chat
copyTradeIdYesCopy trade ID to modify
lossPercentYesStop-loss % (> 0, < 100)
oppositeCopyNoTrade opposite to the trader
traderWalletYesTrader wallet address
copyTradeNameYesLabel
profitPercentYesTake-profit % (> 0)
isChangeStatusNoToggle active/paused relative to the stored state
sessionPrivateKeyNoSession private key
fixedAmountCostPerOrderYesUSD amount (mode 1) or ratio (mode 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv5.1.0
    • changedInput schema / properties / copyMode / description
      Previous value: -"1 = fixed, 2 = proportion"New value: +"1 = fixed USD per order, 2 = proportion"
    • changedInput schema / properties / fixedAmountCostPerOrder / description
      Previous value: -"Amount or ratio"New value: +"USD amount (mode 1) or ratio (mode 2)"
    • changedInput schema / properties / isChangeStatus / description
      Previous value: -"WARNING: Also permanently deletes"New value: +"Toggle active/paused relative to the stored state"
    • changedInput schema / properties / isDelete / description
      Previous value: -"Permanently delete"New value: +"Permanently delete the configuration (positions stay open)"
    • changedInput schema / properties / lossPercent / description
      Previous value: -"Stop-loss %"New value: +"Stop-loss % (> 0, < 100)"
    • addedInput schema / properties / oppositeCopy / description
      Added value: +"Trade opposite to the trader"
    • changedInput schema / properties / profitPercent / description
      Previous value: -"Take-profit %"New value: +"Take-profit % (> 0)"
  2. 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",
-  "copyTradeId",
-  "traderWallet",
-  "copyTradeName",
-  "copyMode",
-  "fixedAmountCostPerOrder",
-  "lossPercent",
-  "profitPercent"
-]New value: +[
+  "copyTradeId",
+  "traderWallet",
+  "copyTradeName",
+  "copyMode",
+  "fixedAmountCostPerOrder",
+  "lossPercent",
+  "profitPercent"
+]
  3. First observedv4.11.3

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description goes well beyond that: it explains that the payload wholly rewrites every field, that isDelete leaves opened positions and their TP/SL orders intact, that isChangeStatus toggles relative to stored state, and that the two flags are mutually exclusive. This is substantial added context for a destructive mutation, though it does not describe the response or confirmation behavior.

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?

Front-loads the routing advice (prefer the specialized siblings), then layers the dangerous edge cases in short declarative clauses. No filler; every sentence conveys an operational constraint.

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 14-parameter destructive mutation with no output schema, it covers the highest-risk behaviors (deletion side effects, toggle semantics, flag conflict, full-payload rewrite) thoroughly. It omits auth/permission prerequisites and return-value expectations, which we'd want but which are partially implied by accountRef/apiKey in the schema.

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%, so baseline would be 3; the description earns extra by stating the mutual-exclusivity constraint between isDelete and isChangeStatus and the full-rewrite requirement, neither of which is expressed in the schema. The rest of the flag semantics largely repeat the schema's own parameter descriptions, so it is not a full 5.

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?

States a specific verb+resource ('Low-level HL perp copy trade update') and immediately qualifies it as low-level, distinguishing it from the specialized siblings. An agent can tell it apart from update_hl_copy_trade_settings without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names four preferred alternatives (update_hl_copy_trade_settings / pause / resume / delete) in the opening sentence, making this the fallback when those don't apply. It also states the precondition that the full current config must be passed, which shapes correct invocation.

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