Skip to main content
Glama

gdex_status

Read-only

Check connected accounts, API reachability, and live trade readiness for each account—funded, unfunded, funding pending, or unreachable—with one next step.

Instructions

Start here. Reports connected accounts (no secrets), API reachability, and per account whether it can trade right now: funded, unfunded, funding_pending or unreachable (read from live balances; unknown is never shown as zero or ready), with one next step. Also delegated policy, pending operations and supported capabilities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gdex_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses meaningful behavior: no secrets are returned, readiness is computed from live balances, and 'unknown is never shown as zero or ready' is an explicit semantic guarantee that prevents misreading a failed lookup as a real state. It also promises a single next step and coverage of delegated policy and pending operations. It doesn't describe latency, caching, or how stale the 'live' balances might be, which keeps it below 5.

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?

'Start here' is front-loaded and each clause carries new information about what the response contains. It is slightly over-dense, packing state enumerations and caveats into nested parentheticals, which costs a little readability, but no sentence is filler.

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 carries the burden of describing returns, and it does enumerate the core response contents (account readiness states, API reachability, delegated policy, pending operations, capabilities, one next step). The exact shape of that response and what the 'next step' looks like (a code, a string, a link) remain unspecified.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The description correctly avoids inventing parameter behavior.

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?

The description names the specific resource (connected accounts, API reachability, delegated policy, pending operations, capabilities) and enumerates the exact trade-readiness states it returns: funded, unfunded, funding_pending, unreachable. That vocabulary is distinct from siblings like get_balances or get_account_state, so an agent can tell what this returns without opening the 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?

'Start here' gives an explicit entry-point instruction and implies the agent should call this before trading or debugging, which is strong when-to-use guidance. It falls short of 5 because it never states when NOT to use it or names the alternatives for a narrower question (e.g. get_balances for raw balances, gdex_accounts for the account list).

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