Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_withdraw_crypto

Request a crypto withdrawal from a Nobitex spot wallet by specifying destination address and amount, or a Lightning invoice, with network and 2FA support.

Instructions

Request a crypto withdrawal.

Args: wallet: Spot wallet id. amount: Amount as a decimal string (omit for Lightning invoices). address: Destination address (omit for Lightning invoices). network: Network name; required for multi-network assets such as USDT. tag: Destination tag/memo where supported. no_tag: Set true to withdraw without a tag. invoice: Lightning invoice (BTCLN), replaces amount/address. explanations: Optional note. totp: 2FA code when the destination is not whitelisted.

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": {
      "wallet": "<wallet>"
    },
    "name": "nobitex_withdraw_crypto"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
totpNo
amountNo
no_tagNo
walletYes
addressNo
invoiceNo
networkNo
explanationsNo

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?

With no annotations, the description carries the full disclosure burden, and it only partially meets it. It usefully reveals that 2FA is required for non-whitelisted destinations and that invoice-based (BTCLN) withdrawals replace amount/address, but it never states that a withdrawal moves funds irreversibly, whether a follow-up confirmation step is required, or what happens on failure.

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 is front-loaded in one sentence and each subsequent line documents exactly one parameter with no filler. The raw "Args:" docstring formatting is slightly unpolished but costs nothing in readability and is proportionate to nine parameters.

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?

For a nine-parameter financial mutation with no annotations and no output schema, the parameter surface is well covered but the operation's consequences and response are not. An agent still cannot tell from this definition whether the call finalizes the withdrawal, needs a confirmation call, or what it returns.

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 description coverage is 0% and all nine parameters are bare titles, so the description must compensate — and it does, explaining each field's meaning plus conditional semantics (invoice replaces amount/address, no_tag suppresses tag, network required for multi-network assets, wallet is a spot wallet id). Minor gaps remain, e.g. the format of wallet ids or what explanations is used for downstream.

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?

The opening line gives a specific verb and resource ("Request a crypto withdrawal"), which is unambiguous about the operation. It does not, however, distinguish this from sibling flows like nobitex_confirm_withdraw or nobitex_cancel_withdraw, nor does it state that this is the crypto rail as opposed to the rial withdrawal tools.

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?

Conditional guidance exists but only at the parameter level: amount/address are "omit for Lightning invoices", network is "required for multi-network assets such as USDT", and totp is needed "when the destination is not whitelisted". There is no tool-level when-to-use/when-not guidance and no mention of the relationship to nobitex_confirm_withdraw or cancel flows.

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