Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_withdrawals

Retrieve crypto withdrawal history with filters for wallet, date range, and pagination to review outgoing transactions and reconcile account activity.

Instructions

List crypto withdrawals.

Args: wallet: Wallet id or "all". from_date: Start date, YYYY-MM-DD. to_date: End date, YYYY-MM-DD. page: Page number. page_size: Items per page.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
walletNo
to_dateNo
from_dateNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it discloses almost nothing beyond "list": no read-only assurance, no authentication/permission requirements, no default page size or maximum page limit, no statement about result ordering or date-range defaults. Only the date format and the special "all" wallet value add operational context.

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?

The one-line summary is front-loaded and the Args block is a compact, scannable enumeration with no filler. Nothing is redundant, though the boilerplate docstring style is functional rather than purposeful prose.

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 five-parameter listing tool with no annotations and no output schema, the description should explain pagination behavior, defaults, and the shape of the returned withdrawal records. None of that is present, so an agent knows the inputs but not what it will get back or how to iterate pages.

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 description coverage is 0%, so the description must compensate, and it does document all five parameters, including two pieces of meaning the schema lacks entirely: the YYYY-MM-DD date format and the "all" sentinel for wallet. It stops short of stating defaults (all parameters are nullable with default null) or the page_size upper bound, which keeps it out of the top score.

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 opening sentence gives a specific verb and resource ("List crypto withdrawals"), which is immediately distinguishable from nobitex_list_deposits or nobitex_list_wallet_transactions. It does not, however, explicitly distinguish crypto withdrawals from the rial-withdrawal-related siblings, so an agent must rely on the tool name alone for that boundary.

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?

There is no guidance on when to call this versus nobitex_list_wallet_transactions, nobitex_list_deposits, or the withdrawal-cancel/confirm tools. No prerequisites, no exclusions, and no mention of whether it covers pending vs completed withdrawals are given; usage is only implied by the tool name.

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