Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_wallets

Retrieve your Nobitex wallets and balances, optionally filtered by wallet type, to inspect spot, margin, credit, or debit account holdings.

Instructions

List the user's wallets and balances.

Args: type: Optional wallet type filter.

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

Input Schema

NameRequiredDescriptionDefault
typeNo

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 are supplied, so the description carries the full disclosure burden, and it discloses almost nothing beyond the operation itself: no auth requirements, no indication of whether balances are in crypto, Rial, or both, no ordering or pagination behavior, and no statement of what an empty result means. It is a read-only listing by implication, but nothing in the text confirms the safety profile.

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 definition is short and front-loaded, with the core operation stated in the first clause. The appended Args block is slightly redundant with the schema but does not bloat the text meaningfully.

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-parameter read tool with no output schema, the description covers the essentials of what it returns at a high level. It is still too thin on return shape and on sibling disambiguation for an agent to choose it confidently among nobitex_get_wallet_balance and nobitex_get_selected_wallets.

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?

With one parameter and effectively 0% description coverage in the schema, the description does add a little: it clarifies that `type` is an optional filter on wallet type rather than a wallet identifier. However, it never enumerates the accepted values (spot, margin, credit, debit), which live only in the schema enum, and it does not explain what omitting the filter returns.

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?

"List the user's wallets and balances" gives a specific verb (list) and resource (wallets/balances), so the core operation is unambiguous. It does not distinguish itself from close siblings such as nobitex_get_wallet_balance or nobitex_get_selected_wallets, leaving the agent to infer which one to call.

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 mention of when to prefer this over nobitex_get_wallet_balance or nobitex_get_selected_wallets, and no prerequisites (e.g. authentication, or whether an empty list is normal). The only usage hint is that the single filter is optional.

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