Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_address_book

Retrieve address-book entries from Nobitex, optionally filtered by network, to review saved wallet addresses for transfers or withdrawals.

Instructions

List address-book entries, optionally filtered by network.

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_list_address_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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, yet it discloses nothing about permissions/auth requirements, pagination or result limits, ordering, or whether this includes only confirmed/whitelisted entries. Beyond implying a read-only listing, no behavioral traits are surfaced.

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?

A single short sentence with the resource front-loaded and the filter qualifier attached to it. There is no filler, hedging, or repetition.

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 low-complexity read tool with one optional parameter and no output schema, the description is minimally adequate: it tells the agent what is listed and that filtering is optional. It falls short on what an entry contains and what network values are valid, which matters given zero schema description coverage.

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 description coverage is 0%, so the description must compensate; it does name the network filter and clarifies that it is optional, which adds meaning beyond the bare 'network' property. However, it gives no example network values or format (e.g. 'BTC', 'ERC20'), leaving an agent to guess acceptable inputs.

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 ('List address-book entries') and states the scoping behavior ('optionally filtered by network'), which distinguishes it from mutation siblings such as nobitex_add_address_book and nobitex_delete_address_book. It does not, however, differentiate itself from other list tools (e.g. nobitex_list_deposit_addresses), which an agent would have to disambiguate by name alone.

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?

The single sentence describes what the tool returns, not when to choose it. There is no guidance on when to use this instead of sibling listings or address-book mutations, and no mention of prerequisites such as authentication or whitelist state.

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