Skip to main content
Glama

Gate DEX MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

dex_auth_gate_login_poll

Destructive

Poll Gate OAuth; returns pending/ok/error. [write] On ok: replace mcp_token unless linked_to_google_session is true. Pass auto_replace_binding=true to rebind exchange UID on new Gate session.

Input Schema

NameRequiredDescriptionDefault
flow_idYesFlow ID returned by dex_auth_gate_login_start
poll_secretYesOne-time poll secret returned by dex_auth_gate_login_start. Do not show this value to the user.
auto_replace_bindingNoIf true and status is ok: when new session walletType is not gate_mcp/gate_quick, call BW POST /v1/wallet/inner/rebind (same as dex_wallet_replace_binding). Gate-native sessions are blocked without calling BW.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / poll_secret
      Added value: +{
+  "description": "One-time poll secret returned by dex_auth_gate_login_start. Do not show this value to the user.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "flow_id"
-]New value: +[
+  "flow_id",
+  "poll_secret"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-idempotent write (readOnlyHint=false, destructiveHint=true, idempotentHint=false), so the safety profile is covered. The description adds genuine context beyond that: it discloses that on 'ok' the mcp_token is replaced unless linked_to_google_session is true, and that auto_replace_binding triggers an exchange-UID rebind. That is real side-effect transparency.

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?

Two dense sentences, purpose front-loaded and side effects conditionally qualifed. The 'linked_to_google_session' reference is used without definition, which is a minor clarity cost, but nothing is wasted.

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?

For a poll tool with mutation side effects and no output schema, the description covers return states and the conditional token/binding changes, which is what an agent needs to act. It leaves 'linked_to_google_session' undefined, a small gap.

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 the scalar params are fully documented in the schema. The description restates the auto_replace_binding purpose ('rebind exchange UID on new Gate session') in slightly less detail than the schema, adding marginal value but relying on the schema for the heavy lifting.

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+resource ('Poll Gate OAuth') and discloses the return states (pending/ok/error), which cleanly differentiates it from the sibling dex_auth_gate_login_start (which begins the flow). The purpose is unambiguous, though it does not name the sibling explicitly.

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

Usage Guidelines3/5

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

Pairing with dex_auth_gate_login_start is implied by 'flow_id returned by dex_auth_gate_login_start' and the poll semantics, but the description never states when to call this versus dex_auth_google_login_poll or when to stop polling. Usage is inferable rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gate DEX MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources