Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_deposits

List crypto deposits with optional wallet filtering and pagination to review transaction history.

Instructions

List crypto deposits.

Args: wallet: Optional wallet id; all wallets when omitted. 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_deposits"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
walletNo
page_sizeNo

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?

With no annotations at all, the description carries the whole burden and does not meet it. It never states that this is a read-only operation, whether authentication is required, what the default paging window is (page and page_size both default to null), or whether results are sorted or bounded in time.

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?

One-line purpose followed by a compact Args block; nothing is padded. The structure is front-loaded and easy to scan, though the Args section is mechanical rather than explanatory.

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 paginated listing call with no annotations, no output schema, and three undocumented-by-schema parameters, the definition is thin. It leaves out pagination defaults, result shape, and ordering, all of which an agent needs to call it correctly and interpret results.

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%, so the Args block is the only documentation. It usefully states that wallet is optional and means all wallets when omitted, which is real added meaning, but "Page number" and "Items per page" say nothing about defaults, maximums, or the behavior when omitted.

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: "List crypto deposits." It is unambiguous about what is returned at a resource level, but it gives no differentiation from look-alike siblings such as nobitex_list_wallet_transactions or nobitex_list_withdrawals, so an agent must infer the 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 when-to-use guidance, no prerequisites, and no mention of alternatives for retrieving transaction history. The only usage-shaped information is implicit in the Args block.

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