Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_cancel_withdraw

Cancel a pending crypto withdrawal on Nobitex to stop an unwanted transaction before it is processed.

Instructions

Cancel a pending crypto withdrawal.

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": {
      "withdraw": "<withdraw>"
    },
    "name": "nobitex_cancel_withdraw"
  }
}

Input Schema

NameRequiredDescriptionDefault
withdrawYes

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 provided, so the description must carry the full behavioral burden. It discloses that this is a cancellation of a pending crypto withdrawal, implying a destructive mutation, but it does not explain whether cancellation is final, what happens to reserved funds, whether authentication is required, or what errors occur for non-pending withdrawals.

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?

The description is a single front-loaded sentence with no filler. Every word contributes to the stated purpose, even though the overall definition remains under-specified elsewhere.

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 one-parameter destructive operation with no annotations and no output schema, the definition is too sparse. It identifies the action but omits the meaning of the required parameter and the consequences or conditions of cancellation, leaving an agent with significant uncertainty before invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required integer parameter named 'withdraw', but schema description coverage is 0% and the description never explains what that integer represents. An agent cannot tell from the definition whether it is a withdrawal ID, amount, or another identifier.

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: cancel a pending crypto withdrawal. The word 'crypto' distinguishes it from the sibling nobitex_cancel_rial_withdrawal, and 'pending' scopes when it applies. It stops short of explicitly naming the alternative or confirming the withdrawal identifier, but the core purpose is clear.

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 usage signal is that the withdrawal must be pending. The description does not say when to use this instead of confirm_withdraw, cancel_rial_withdrawal, or other cancel tools, and it gives no prerequisites or exclusions.

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