Skip to main content
Glama
GemachDAO

GDEX Trading

by GemachDAO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

place_perp_order

Destructive

Places a simple perpetual futures order on HyperLiquid as a market or reduce-only limit order, specifying long or short, price, and contract size.

Instructions

Place a simple perp order on HyperLiquid without TP/SL. isMarket=true (default) is sent via /hl/create_order as a market order; isMarket=false sends a limit order at price via /hl/place_order, which the backend currently accepts only with reduceOnly=true.

Input Schema

NameRequiredDescriptionDefault
coinYesAsset symbol
sizeYesPosition size in contracts
priceYesPrice in USD ('0' with isMarket=true uses the mark price)
apiKeyNoGDEX API key for AES encryption
isLongYesTrue for long, false for short
isMarketNoTrue for market (via create_order), false for limit
accountRefNoConnected account from gdex_connect. Supplies session key, wallet address, API key and session data so no secret is passed in chat
reduceOnlyNo
walletAddressNoControl wallet address
sessionPrivateKeyNoSession private key from sign-in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
+}
    • addedInput schema / properties / isMarket / description
      Added value: +"True for market (via create_order), false for limit"
    • changedInput schema / properties / price / description
      Previous value: -"Price in USD"New value: +"Price in USD ('0' with isMarket=true uses the mark price)"
    • changedInput schema / required
      Previous value: -[
-  "apiKey",
-  "walletAddress",
-  "sessionPrivateKey",
-  "coin",
-  "isLong",
-  "price",
-  "size"
-]New value: +[
+  "coin",
+  "isLong",
+  "price",
+  "size"
+]
  2. First observedv4.11.3

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the existing destructiveHint and openWorldHint annotations, the description discloses backend routing details: market orders go via /hl/create_order, while limit orders go via /hl/place_order and are currently accepted only with reduceOnly=true. It still omits authentication/session requirements and any response behavior, but the added backend constraint is substantive.

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 two efficient sentences, front-loading the purpose and then the key branching behavior. Every sentence carries relevant information with no repetition.

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 10-parameter destructive trading tool, the description covers the critical behavioral nuance and a current backend limitation. The input schema documents most parameters, but no output schema exists and the description does not explain return values or session/auth expectations, leaving a minor gap.

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 already high at 90%, so the baseline is 3. The description adds useful meaning for isMarket, price, and reduceOnly by explaining the market-vs-limit path and the backend restriction on limit orders.

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: placing a HyperLiquid perp order without TP/SL. It adds meaningful scope, but does not explicitly differentiate itself from siblings such as open_perp_position or execute_cross_perp/execute_isolated_perp.

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?

It explains the isMarket=true vs isMarket=false branch and the current reduceOnly constraint for limit orders. However, it does not explicitly say when to choose this tool over sibling perp-order or position-management tools.

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