Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_generate_deposit_address

Generate a blockchain deposit address for a Nobitex spot wallet or specified currency and network, with default or legacy address type.

Instructions

Generate a blockchain deposit address.

Args: wallet: Spot wallet id. currency: Currency code when wallet is omitted. network: Network name. address_type: Address type, "default" or "legacy".

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": "nobitex_generate_deposit_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletNo
networkNo
currencyNo
address_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It does not say whether generation is idempotent (returns an existing address vs. minting a new one), whether it requires authentication or whitelisting, what rate limits apply, or what the call returns (address plus tag/memo).

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?

One-line purpose sentence up front, followed by a short arg list with no filler. It reads as a pasted docstring rather than prose tuned for an agent, but it is compact and front-loaded.

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 tool with four optional parameters, no annotations, and no output schema, the description should clarify the wallet-vs-currency requirement, which network values are valid, and roughly what comes back. Only the parameter glossary is covered, leaving the invocation contract underspecified.

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 documents all four parameters and adds real meaning: wallet is a 'Spot wallet id', address_type is restricted to 'default' or 'legacy', and currency is only relevant 'when wallet is omitted'. That conditional relationship is not expressible in the flat schema.

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 and resource: 'Generate a blockchain deposit address.' An agent immediately knows the operation, though nothing distinguishes it from the sibling nobitex_generate_deposit_address_v2, which by name alone appears to overlap.

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?

No when-to-use, when-not-to-use, or alternative routing is provided despite a near-identical v2 sibling. The only implicit guidance is the param note 'Currency code when wallet is omitted', which hints at a wallet/currency choice but does not explain it as a rule.

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