Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_confirm_withdraw

Confirm a pending withdrawal by submitting the withdrawal ID returned at request time, plus the SMS OTP when required.

Instructions

Confirm a pending withdrawal.

Args: withdraw: Withdrawal id returned by the request step. otp: SMS one-time code when required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "withdraw": "<withdraw>"
    },
    "name": "nobitex_confirm_withdraw"
  }
}

Input Schema

NameRequiredDescriptionDefault
otpNo
withdrawYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not say that confirming moves funds irreversibly, whether a confirmed withdrawal can still be cancelled, how long OTP validity lasts, what errors occur on a bad code, or whether the call is idempotent — all critical for a financial mutation.

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?

The purpose sentence is front-loaded and the Args block is compact with no filler. The docstring-style formatting is slightly boilerplate but each line carries useful parameter information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters and no output schema, the description covers the mechanics adequately. For an unannotated, irreversible financial mutation, though, it omits outcome and safety details an agent would need before invoking it.

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?

Schema coverage is 0%, yet the description explains both parameters: the withdrawal id originates from the request step, and OTP is an SMS one-time code needed only sometimes. That adds real meaning beyond the bare "integer"/"string|null" schema, though it omits format or expiry details for the code.

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?

"Confirm a pending withdrawal" gives a specific verb and resource, and the Args block clarifies it is the second step of a withdrawal flow. It does not explicitly distinguish itself from cancel-withdraw siblings, but the purpose is unambiguous.

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?

The phrase "Withdrawal id returned by the request step" implies this must follow a prior request call, and "when required" signals OTP is conditional. However, there is no explicit when-to-use/when-not guidance, no mention of pairing with nobitex_cancel_withdraw or nobitex_withdraw_crypto, and no stated preconditions such as withdrawal being in a pending state.

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