Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_rial_withdrawal

Retrieve details for a single rial withdrawal using its CW-, WJ-, or W-prefixed ID to check status and transaction data.

Instructions

Get details of one rial withdrawal (id prefixed CW/WJ/W).

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

Input Schema

NameRequiredDescriptionDefault
withdraw_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'Get' signals a read-only lookup, and the ID prefix hint (CW/WJ/W) is genuinely useful context beyond the schema. It says nothing about error behavior for unknown IDs, permissions, or what 'details' encompasses, leaving real gaps.

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?

One short sentence, front-loaded with the verb and resource, and the qualifier appears immediately. No wasted wording.

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 simple single-record read tool with one required parameter and no output schema, the description covers the essentials. Missing are the read-only confirmation, behavior on invalid/unknown IDs, and any hint of what fields come back.

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 coverage is 0% and the single parameter is bare ('Withdraw Id'), so the description must compensate; it does by specifying the accepted ID prefixes CW/WJ/W, which is concrete guidance not present in the schema. It stops short of stating whether the ID is numeric-only after the prefix.

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+resource ('Get details of one rial withdrawal') and scopes it to a single record, which distinguishes it from the list/request/cancel withdrawal siblings. It does not explicitly contrast with the generic nobitex_get_withdrawal, so it falls 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 Guidelines3/5

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

Usage is implied by 'one ... withdrawal' — call it when you already have a specific withdrawal ID — but the description never states when to prefer this over nobitex_get_withdrawal or nobitex_list_rial_withdraw_banks, nor any prerequisites.

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