Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_wallet_balance

Retrieve the current balance of a single Nobitex wallet by specifying its currency symbol, such as btc or rls, to check available funds.

Instructions

Get the balance of one currency wallet.

Args: currency: Currency symbol, e.g. "btc" or "rls".

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": {
      "currency": "<currency>"
    },
    "name": "nobitex_get_wallet_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and does not meet it. It never says whether authentication is required, whether the balance reflects available versus blocked/in-order funds, or what the response looks like — all material for a financial balance query.

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?

Two lines, front-loaded with the action, followed by a compact Args block. The docstring formatting is slightly machine-flavored but nothing is wasted or vague.

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 single-parameter read tool with no output schema, the description is minimally adequate but omits what the returned balance represents and any auth/permission context. An agent could call it, but might misread the result.

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: it supplies concrete example values ("btc", "rls") and clarifies that "rls" (rial) counts as a currency symbol, which the bare schema title "Currency" does not convey. It stops short of stating case sensitivity or the full symbol set.

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: "Get the balance of one currency wallet." The singular "one currency wallet" implicitly distinguishes it from the sibling nobitex_get_wallets (plural), though it never names that alternative explicitly.

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 only implied by the tool name and the word "one" — an agent can infer this is the single-currency lookup versus an all-wallets listing, but there is no explicit when-to-use statement, no prerequisites, and no named alternative.

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