Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_generate_deposit_address_v2

Creates a new deposit address for a chosen coin and network, with an optional title, so users can receive cryptocurrency deposits.

Instructions

Generate a new deposit address (multi-address API).

Args: coin: Coin symbol. network: Network name. title: Optional address title.

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": {
      "coin": "<coin>",
      "network": "<network>"
    },
    "name": "nobitex_generate_deposit_address_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYes
titleNo
networkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 behavioral burden. It does not say whether generating an address invalidates prior addresses, whether it requires whitelisting or specific permissions, whether repeated calls create duplicates, or what the response contains — all material for a state-creating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded and clear, but the Args block adds no information beyond the schema and is pure duplication. It is short, but a meaningful fraction of that brevity is wasted on restatement.

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?

This is an unannotated mutation tool with no output schema and zero parameter documentation in the schema. For that complexity profile the description should cover permissions, effects on existing addresses, required network values, and return shape; it covers none of these.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, yet it only restates the parameter names ('coin: Coin symbol', 'network: Network name', 'title: Optional address title'). No accepted symbols, network naming convention, coin/network pairing rules, or title constraints are given. The one useful fact, that title is optional, is already in the schema as default null.

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 new deposit address'. The parenthetical '(multi-address API)' gestures at a distinction from the sibling nobitex_generate_deposit_address, but the meaning of 'multi-address' is never explained, so the differentiation is only partial.

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 the near-identical sibling nobitex_generate_deposit_address, and no prerequisites (whitelist status, network availability, whether old addresses remain valid). The only usage hint is the unexplained '(multi-address API)' tag.

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