Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_request_rial_withdrawal

Request a rial withdrawal from your Nobitex account to a verified bank account by specifying the account ID and amount; the withdrawal fee is deducted from the total.

Instructions

Request a rial withdrawal to a verified bank account.

Args: destination_bank_account_id: Verified bank account id. amount: Total amount in rial as a decimal string (fee is deducted).

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": {
      "destination_bank_account_id": "<destination_bank_account_id>",
      "amount": "<amount>"
    },
    "name": "nobitex_request_rial_withdrawal"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
destination_bank_account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations at all, so the description carries the full behavioral burden. It usefully discloses that the fee is deducted from the amount, but omits critical behavior for a financial mutation: whether the request is pending vs executed, whether confirmation is required, limits, and what happens on failure.

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?

Short and front-loaded, with the Args block mapping cleanly to the two required parameters. Every sentence carries information; no padding or repetition.

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?

For a two-parameter financial mutation with no annotations and no output schema, the description should say more about the resulting state of the request and any prerequisites. As written, an agent knows what to send but not what it will get back or what conditions must hold first.

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

Parameters3/5

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

Schema coverage is 0%, and the description does document both parameters: the account must be verified, and amount is a decimal string in rial with the fee deducted. That said, it does not explain formatting edge cases (decimals, minimums) or how the account id is obtained, leaving gaps for a 0%-coverage schema.

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?

States a specific verb and resource: 'Request a rial withdrawal to a verified bank account'. The rial context and 'verified bank account' constrain it enough to distinguish it from crypto withdrawal siblings, though it never explicitly contrasts with nobitex_cancel_rial_withdrawal or nobitex_get_rial_withdrawal.

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?

No when-to-use guidance, no stated prerequisites (whitelist activation, 2FA, emergency-cancel code) and no named alternatives. The only hint is the word 'verified', which implies the account must already be confirmed, but the agent must infer that entirely.

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