Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_add_address_book

Add a cryptocurrency address to the Nobitex address book by providing network, address, and OTP/TOTP codes in one legacy-flow step.

Instructions

Add an address-book entry in one step (legacy flow).

Args: title: Address title. network: Network name. address: Destination address. otp_code: SMS/email one-time code. tfa_code: TOTP two-factor code. tag: Optional tag/memo.

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": {
      "title": "<title>",
      "network": "<network>",
      "address": "<address>",
      "otp_code": "<otp_code>",
      "tfa_code": "<tfa_code>"
    },
    "name": "nobitex_add_address_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
titleYes
addressYes
networkYes
otp_codeYes
tfa_codeYes

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 does not disclose whether the entry is usable immediately or needs a follow-up confirmation, whether the write is reversible, what permissions or whitelist state are required, or what happens on a bad OTP/TFA code; the only behavioral signal is the required OTP and TFA parameters, which the schema already exposes via the required list.

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 leading sentence is front-loaded and efficient, but the remainder is a raw docstring parameter dump rather than prose tailored to an agent. It contains no filler, yet the structure is mechanical and the "Args:" formatting wastes little but adds little.

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 six-parameter, five-required mutation with no annotations and no output schema, the description covers the inputs but not the outcome: it never says whether the call alone finalizes the entry or requires the sibling confirm step, nor what a success response contains. That is a meaningful gap for a write operation on a financial account.

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. The Args list glosses all six parameters and usefully disambiguates otp_code (SMS/email one-time code) from tfa_code (TOTP two-factor code), but glosses like "Network name" and "Address title" add almost nothing, and the valid network values or address format remain undefined.

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 first sentence gives a specific verb and resource ("Add an address-book entry") and adds scope with "in one step (legacy flow)", which hints that a multi-step sibling flow exists. It stops short of naming that alternative, so an agent cannot be fully certain how this differs from nobitex_create_address_book_item / nobitex_confirm_address_book_item without opening the schemas.

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 only guidance is the parenthetical "legacy flow", which implies a newer preferred path but never says when to choose this one versus the create/confirm siblings. There is no statement of prerequisites, no exclusion, and no routing advice, leaving the agent to guess.

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