Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_transfer_between_wallets

Transfers funds between spot and margin wallets by specifying currency, amount, source, and destination.

Instructions

Transfer funds between the spot and margin wallets.

Args: currency: Currency name. amount: Amount as a decimal string. src: Source wallet, "spot" or "margin". dst: Destination wallet, "spot" or "margin".

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": {
      "currency": "<currency>",
      "amount": "<amount>",
      "src": "<src>",
      "dst": "<dst>"
    },
    "name": "nobitex_transfer_between_wallets"
  }
}

Input Schema

NameRequiredDescriptionDefault
dstYes
srcYes
amountYes
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 reveals that this is a fund-moving mutation between two account types but says nothing about immediacy, fees, minimum/maximum amounts, failure modes, or reversibility — significant gaps for a financial mutation. The wallet-list sentence largely restates the schema enum rather than adding new behavioral context.

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 description is short and front-loads the operation in a single sentence before the Args list. The Args block is partly redundant with the schema's titles and enums, which is the only inefficiency.

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

Completeness2/5

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

For a required-argument financial mutation with no annotations, no output schema, and 0% schema description coverage, the definition is too thin. It does not indicate what the call returns (transfer status or ID), whether it is atomic, or what preconditions must hold, leaving the agent to guess at operational behavior.

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 0%, so the description must compensate. It does document all four parameters, and 'amount as a decimal string' adds a genuine format constraint beyond the bare 'Amount' title, but 'currency: Currency name' and the src/dst 'spot' or 'margin' notes remain shallow and do not clarify symbol conventions (e.g., 'btc' vs 'BTC') or units.

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 description gives a specific verb and resource: 'Transfer funds between the spot and margin wallets,' which an agent can immediately match to a wallet-transfer operation. It does not explicitly contrast with any sibling tool, but the purpose itself is unambiguous rather than tautological.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, no prerequisites (e.g., whether a margin position or sufficient spot balance is required), and no exclusions. The only usable constraint is the src/dst wallet values, which the schema already enumerates.

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