Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_selected_wallets

Retrieve selected Nobitex wallets, optionally filtering results by comma-separated currencies or wallet type, to inspect specific account balances.

Instructions

List selected wallets, optionally filtered by currencies.

Args: currencies: Comma-separated currency list, e.g. "btc,usdt". 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_selected_wallets"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
currenciesNo

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 behavioral burden. It implies a read-only list but never says so, and says nothing about authentication requirements, pagination/limits, whether balances or addresses are included per wallet, or what happens when filters match nothing.

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 core sentence is front-loaded and the whole thing is short with no filler. The Args block is a bit redundant (the type entry essentially restates the parameter name) and reads like auto-generated docstring scaffolding, but nothing is bloated.

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 tool with no annotations and no output schema, the description should say more about what a "selected wallet" contains and what the response looks like. As written, an agent knows how to pass currencies but not what it will get back or how to interpret the filters' interaction.

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 description coverage is 0%, so the description must compensate. It does this well for currencies, specifying the comma-separated format and an example ("btc,usdt") that the schema's bare string type does not convey, but the type parameter is described only as "Optional wallet type filter," restating its name rather than explaining the spot/margin/credit/debit semantics or defaults.

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 selected wallets" gives a specific verb and resource, and "optionally filtered by currencies" scopes it. It does not explicitly contrast itself with the sibling nobitex_get_wallets, so the distinction between "selected" and all wallets is left implicit, but an agent can still tell what this returns better than from the name alone.

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 statement of when to call this versus nobitex_get_wallets, nor any prerequisites, exclusions, or edge cases. The only usage signal is the word "optionally" on the currency filter, which is implied rather than guidance.

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