Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_delete_address_book

Deletes an address-book entry by its ID. Use it to remove saved cryptocurrency wallet addresses from the Nobitex account.

Instructions

Delete an address-book entry by id.

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": {
      "address_id": "<address_id>"
    },
    "name": "nobitex_delete_address_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
address_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 for a destructive mutation, yet it only restates the verb. It says nothing about irreversibility, whether confirmation or 2FA is required, what happens if the id is unknown, or what the call returns.

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?

A single front-loaded sentence with zero filler and no redundancy. Its brevity is efficient, though it borders on under-specification rather than optimal structuring.

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 destructive, single-parameter mutation with no annotations and no output schema, the definition is too thin. An agent lacks the irreversibility warning, id provenance, and error behavior needed to invoke it safely.

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 single parameter 'address_id' is undocumented in the schema. The phrase 'by id' only weakly signals that the integer identifies an address-book entry; it gives no format, origin (e.g. from nobitex_list_address_book), or constraint details, so the coverage gap is not compensated.

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 names a specific verb and resource ('Delete an address-book entry') and adds a lookup key ('by id'), which separates it from sibling mutations such as nobitex_delete_api_key, nobitex_delete_bank_account, and nobitex_delete_bank_card. It is clear what the tool acts on, though it does not explicitly contrast itself with those siblings.

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 choose this over the other destructive siblings, no preconditions (e.g. the entry must exist or be unconfirmed), and no warning about when deletion is inappropriate. The agent must infer everything from the tool name.

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