Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_cancel_rial_withdrawal

Cancel a pending rial withdrawal by providing its withdrawal ID, stopping the transaction before it is processed.

Instructions

Cancel a pending rial 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_id": "<withdraw_id>"
    },
    "name": "nobitex_cancel_rial_withdrawal"
  }
}

Input Schema

NameRequiredDescriptionDefault
withdraw_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 signals a state-changing, effectively destructive operation but says nothing about whether funds are returned, whether cancellation is reversible, what happens if the withdrawal is already processed, or what auth/rate limits apply.

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 single sentence is front-loaded and waste-free, but it is under-specified rather than efficiently concise for a mutation tool. There is room for a clause on preconditions without bloat.

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 mutation tool with no annotations, no output schema, and a fully undocumented parameter, the definition leaves out preconditions, failure modes, and result behavior. An agent could call it but cannot predict or handle outcomes confidently.

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% and the description never mentions withdraw_id or its expected format (numeric ID vs. token) or where to obtain it. With one undocumented required parameter, the description fails to compensate for the schema gap.

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 gives a specific verb and resource ('Cancel a pending rial withdrawal'), and the 'rial' qualifier distinguishes it from the generic nobitex_cancel_withdraw sibling. It does not explicitly name or route against those siblings, keeping it short of a 5.

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 word 'pending' implies a precondition, but there is no explicit when-to-use guidance, no statement of what to do for a non-pending withdrawal, and no mention of the sibling nobitex_cancel_withdraw as an alternative. The agent must infer selection criteria.

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