Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_activate_emergency_cancel

Activate emergency withdrawal cancellation to halt pending withdrawals during an account security event.

Instructions

Activate emergency withdrawal cancellation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only says 'activate.' It does not state that this is a state-changing mutation, whether activation is reversible or time-limited, what permissions or confirmations are required, or what side effects occur on withdrawals. For a zero-annotation mutation tool this is a substantial gap.

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 description is a single short sentence with no wasted words, but its brevity stems from under-specification rather than economy. There is no front-loaded statement of effect or consequence to orient the agent.

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 no-annotation, no-output-schema mutation tool, the description does not convey enough for safe invocation: no indication of state change, irreversibility, required prior steps, or result. Only the parameter dimension is adequately covered by the empty schema.

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?

The tool takes zero parameters and the schema is an empty object with full coverage, so this is the baseline 4 case; there are no parameter semantics for the description to explain. The description neither helps nor hurts here, though it could have noted that the call requires no arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description essentially restates the tool name 'activate_emergency_cancel' as 'Activate emergency withdrawal cancellation,' without clarifying what object is being activated or what an emergency cancellation is in this context. It is closer to tautology than a distinct verb+resource statement, and it does not distinguish the tool from siblings such as nobitex_get_emergency_cancel_code or nobitex_cancel_withdraw.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given, and no prerequisites (for example, whether an emergency cancel code from nobitex_get_emergency_cancel_code must be obtained first) are mentioned. The agent is left to infer all usage conditions from the name alone.

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