Skip to main content
Glama
GemachDAO

GDEX Trading

by GemachDAO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_balances

Read-only

Read token balances for a managed GDEX wallet on a specified chain, optionally filtered to one token, so agents can check holdings before trading.

Instructions

Token balances of the managed GDEX wallet on one chain, optionally one token. [] means the backend reported no holdings; a failed read errors. Native balance: get_trading_funds.

Input Schema

NameRequiredDescriptionDefault
dataNoEncrypted session data, instead of sessionPrivateKey + apiKey
chainYesChain identifier
apiKeyNoGDEX API key (with sessionPrivateKey)
accountRefNoConnected account from gdex_connect. Supplies session key, wallet address, API key and session data so no secret is passed in chat
tokenAddressNoOptional token filter
walletAddressNoControl wallet address (the GDEX userId), not the managed trading wallet
sessionPrivateKeyNoSession private key from sign-in (with apiKey)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv5.1.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 / apiKey
      Added value: +{
+  "description": "GDEX API key (with sessionPrivateKey)",
+  "type": "string"
+}
    • addedInput schema / properties / data
      Added value: +{
+  "description": "Encrypted session data, instead of sessionPrivateKey + apiKey",
+  "type": "string"
+}
    • addedInput schema / properties / sessionPrivateKey
      Added value: +{
+  "description": "Session private key from sign-in (with apiKey)",
+  "type": "string"
+}
    • changedInput schema / properties / walletAddress / description
      Previous value: -"Wallet address"New value: +"Control wallet address (the GDEX userId), not the managed trading wallet"
    • changedInput schema / required
      Previous value: -[
-  "walletAddress",
-  "chain"
-]New value: +[
+  "chain"
+]
  2. First observedv4.11.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real behavioral detail beyond that: '[] means the backend reported no holdings; a failed read errors' discloses empty-result and failure semantics. It stops short of describing auth requirements or what the returned balance fields look like.

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?

Three short, front-loaded statements with no filler: the scope comes first, then empty/error semantics, then the sibling hand-off. Every clause earns its place.

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?

With no output schema, the description usefully covers return-shape expectations (empty array) and failure behavior, and it disambiguates the managed trading wallet from the control wallet. The auth/session path is left entirely to the schema, which is acceptable given 100% coverage.

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 coverage is 100%, so all seven parameters are already documented in the schema; the description only restates the chain and token filters implicitly. Baseline 3 is appropriate since the schema carries the parameter burden.

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+scope: token balances of the managed GDEX wallet on one chain, optionally filtered to one token. It also names the sibling it is not (native balance -> get_trading_funds), so an agent can route without opening either schema.

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

Usage Guidelines4/5

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

Clear when-to-use context (managed wallet, single chain, optional token filter) and explicitly routes native-balance queries to get_trading_funds. It does not address other balance-adjacent siblings like usdc_get_balances or get_wallet_info, so no full exclusion set.

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