Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_deactivate_whitelist

Disable secure-withdrawal (whitelist) mode by submitting an SMS/email one-time code and TOTP two-factor code.

Instructions

Disable secure-withdrawal (whitelist) mode.

Args: otp_code: SMS/email one-time code. tfa_code: TOTP two-factor code.

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": {
      "otp_code": "<otp_code>",
      "tfa_code": "<tfa_code>"
    },
    "name": "nobitex_deactivate_whitelist"
  }
}

Input Schema

NameRequiredDescriptionDefault
otp_codeYes
tfa_codeYes

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 provided, so the description carries the full burden. It discloses the authentication requirement (SMS/email OTP plus TOTP) but says nothing about the consequences of disabling whitelist mode, such as whether registered addresses are removed, whether withdrawals become unrestricted, or whether there is a cooldown or irreversibility. For a security-weakening mutation this is a significant gap.

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 states the action, followed by compact per-argument notes. Nothing is wasted, though the Args block is minimal rather than richly structured.

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?

With no output schema and no annotations, the description should compensate more, but for a two-parameter account-mode toggle it covers the action and both inputs adequately. The missing piece is what actually changes on the account after deactivation.

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% and the schema titles are merely 'Otp Code' and 'Tfa Code', so the description meaningfully clarifies that otp_code is an SMS/email one-time code and tfa_code is a TOTP two-factor code. That is real added meaning over the schema, though it does not specify format or length.

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: 'Disable secure-withdrawal (whitelist) mode.' An agent can immediately tell this is the inverse of nobitex_activate_whitelist, though the sibling is never named explicitly. It is clear but lacks explicit sibling differentiation.

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 alternatives, no prerequisites (such as requiring whitelist mode to already be enabled), and no warning about the security implications of disabling withdrawal protection. The only implied usage is that both codes must be supplied.

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