Skip to main content
Glama
GemachDAO

GDEX Trading

by GemachDAO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

perp_deposit

Destructive

Deposit USDC into HyperLiquid perpetual accounts on GDEX Trading. Move USDC from Arbitrum to the required trading ledger.

Instructions

Deposit USDC into the HyperLiquid perpetual account from Arbitrum.

Input Schema

NameRequiredDescriptionDefault
amountYesUSDC amount to deposit, e.g. '100'. Min 10 USDC.
apiKeyNoGDEX API key for AES encryption
chainIdNoChain ID (must be 42161 = Arbitrum)
accountRefNoConnected account from gdex_connect. Supplies session key, wallet address, API key and session data so no secret is passed in chat
tokenAddressYesUSDC token address on Arbitrum
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",
-  "tokenAddress",
-  "amount"
-]New value: +[
+  "tokenAddress",
+  "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 flag this as a non-read-only, destructive, open-world operation, so the safety profile is covered structurally. The description adds only the source chain (already encoded as chainId default 42161 in the schema) and does not disclose that funds leave the Arbitrum wallet irreversibly, that a session/API-key context is required, or what follows a successful deposit.

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 naming verb, asset, destination and source chain, with no redundant restatement of the name. It is efficient, though its terseness is part of why coverage elsewhere is thin.

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?

For a destructive, real-money funding operation with no output schema, one sentence is inadequate: prerequisites (accountRef/session key, trading enabled), the minimum amount, bridge/settlement behavior and failure modes are all absent. The agent knows what it does but not how to invoke it safely.

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% with 7 fully documented parameters, so the schema carries the load and baseline 3 applies. The description contributes no parameter detail beyond what the schema already states.

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?

Specific verb (Deposit), asset (USDC), destination (HyperLiquid perpetual account) and source chain (Arbitrum) are all stated, which cleanly pairs it against the sibling perp_withdraw. It does not, however, explicitly distinguish itself from adjacent funding paths like execute_cross_perp or hl_swap_collateral, so an agent operating near those tools gets no routing cue.

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 when-to-use guidance, no prerequisites (e.g. that an accountRef from gdex_connect or a session key is expected), and no mention of the 10 USDC minimum enforced by the schema. The agent must infer all preconditions from sibling 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