Skip to main content
Glama
GemachDAO

GDEX Trading

by GemachDAO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

perp_withdraw

Destructive

Withdraw USDC from a HyperLiquid perpetual account by specifying the amount, enabling traders to move funds out of their perp balance to a connected wallet.

Instructions

Withdraw USDC from the HyperLiquid perpetual account.

Input Schema

NameRequiredDescriptionDefault
amountYesUSDC amount to withdraw
apiKeyNoGDEX API key for AES encryption
accountRefNoConnected account from gdex_connect. Supplies session key, wallet address, API key and session data so no secret is passed in chat
walletAddressNoControl wallet address
sessionPrivateKeyNoSession private key from sign-in

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",
-  "walletAddress",
-  "sessionPrivateKey",
-  "amount"
-]New value: +[
+  "amount"
+]
  2. First observedv4.11.3

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds no behavioral context beyond that: it doesn't say where the USDC goes (control wallet vs. elsewhere), whether partial withdrawals are allowed, fees, minimums, or irreversibility. For a fund-moving mutation, this is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient but under-specified rather than padded, so it earns a 4 rather than a 5.

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, five-parameter financial mutation with no output schema, so the description should carry the auth/session requirements and the destination of withdrawn funds. Instead it only restates the name, leaving the agent to reverse-engineer requirements from the schema.

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 every parameter is documented in the schema, including the amount string and the credential fields. The description adds nothing beyond restating USDC and the account, 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?

States a specific verb and resource: withdraw USDC from the HyperLiquid perpetual account. Clear on its own, but it does not distinguish itself from neighboring money-movement tools such as perp_deposit, transfer_native, or usdc_convert_native, so an agent must infer the boundary.

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 guidance on when to use this versus perp_deposit, transfer_native, or the bridge tools, and no mention of prerequisites (a gdex_connect session, API key, signing). The schema hints at these, but the description itself routes nothing.

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