Skip to main content
Glama
GemachDAO

GDEX Trading

by GemachDAO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

limit_sell

Destructive

Create a limit sell order to sell a token when its USD price reaches your target, automatically classifying the order as take-profit or stop-loss.

Instructions

Create a limit sell order — sell a token when price reaches target. Auto-classifies as TP or SL.

Input Schema

NameRequiredDescriptionDefault
amountYesToken amount in raw units (token decimals), a positive integer string
apiKeyNoAPI key for AES encryption
userIdNoControl wallet address
chainIdYesNumeric chain ID
accountRefNoConnected account from gdex_connect. Supplies session key, wallet address, API key and session data so no secret is passed in chat
tokenAddressYesToken address to sell
triggerPriceYesUSD price at which to trigger the sell (plain decimal)
sessionPrivateKeyNoSession private key from sign-in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.1.0
    • changedInput schema / properties / amount / description
      Previous value: -"Token amount in raw units"New value: +"Token amount in raw units (token decimals), a positive integer string"
    • changedInput schema / properties / triggerPrice / description
      Previous value: -"USD price at which to trigger the sell"New value: +"USD price at which to trigger the sell (plain decimal)"
  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",
-  "chainId",
-  "tokenAddress",
-  "amount",
-  "triggerPrice"
-]New value: +[
+  "chainId",
+  "tokenAddress",
+  "amount",
+  "triggerPrice"
+]
  3. First observedv4.11.3

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuine behavioral detail — the order is auto-classified as TP or SL — but says nothing about credential/auth paths, whether funds are escrowed, or how to cancel the resulting order.

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 tight sentences with the action and trigger front-loaded and zero filler. Nothing is repeated unnecessarily and every clause carries meaning.

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

Completeness3/5

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

For a destructive, open-world mutation tool with three competing credential parameters and no output schema, the description is thinner than it should be. It omits what the call returns (order id?), how the TP/SL classification is decided, and what lifecycle follow-up (get_limit_orders / direct_cancel_order) applies.

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% across all 8 parameters, including amount, triggerPrice, and the three credential fields, so the schema carries the load. The description only restates 'sell a token' and 'price reaches target' without adding format or ordering semantics beyond what the schema provides.

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?

States a specific verb and resource ("Create a limit sell order") plus the triggering condition ("sell a token when price reaches target"), which is enough to distinguish it from limit_buy. It does not, however, name the market-sell or managed alternatives it competes with, so sibling differentiation is implicit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The description never tells the agent how this differs from sell_token, managed_sell, gdex_execute_trade, or place_perp_order, nor what prerequisites (accountRef vs apiKey vs sessionPrivateKey) must be satisfied before calling.

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