Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_deposit_addresses

List generated deposit addresses for a specific coin and network, with filters for status, title search, sort order, and pagination to review wallet deposit addresses.

Instructions

List generated deposit addresses for a coin/network.

Args: network: Network name, e.g. "ETH". coin: Coin symbol, e.g. "eth". ordering: Sort by creation time, newest first by default. is_disabled: true = disabled only, false = active only. search: Substring search on address title. page: Page number. page_size: Items per page.

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

Input Schema

NameRequiredDescriptionDefault
coinYes
pageNo
searchNo
networkYes
orderingNo
page_sizeNo
is_disabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. The verb "List" implies a read-only operation, and the default ordering behavior is disclosed, but authentication requirements, default treatment of disabled addresses when is_disabled is null, and return shape are not described.

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

Conciseness5/5

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

The purpose is front-loaded in one sentence, followed by a compact parameter list. Every line is useful and there is no redundant wording.

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 seven-parameter list tool with no annotations and no output schema, the definition is adequate for invocation because all parameters are described. However, it does not explain the return payload, pagination behavior, or how disabled addresses are handled by default.

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%, so the description must compensate, and it does: it explains network, coin, ordering, is_disabled, search, page, and page_size. It could be stronger by mapping the ordering enum values and specifying pagination defaults or limits, but it adds substantial meaning beyond the 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?

The description states a specific verb and resource: list generated deposit addresses for a given coin/network. It is clearly distinguishable from sibling tools that generate addresses or update address titles, though it does not explicitly name those alternatives.

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?

Usage is implied: call this to retrieve existing generated deposit addresses. The description does not explicitly say when to use it versus generating a new deposit address, updating a title, or listing the address book.

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