Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_wallet_transactions

Lists transactions for a specific Nobitex wallet with pagination and optional detail level, helping you review wallet activity and transaction history.

Instructions

List transactions for a single wallet.

Args: wallet: Wallet id. page: Page number. page_size: Items per page. details: Detail level.

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": {
      "wallet": "<wallet>"
    },
    "name": "nobitex_list_wallet_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
walletYes
detailsNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it meets little of it: nothing about whether results are paginated, what the defaults for page/page_size are, how far back history goes, or what fields come back. Only 'List' weakly implies a read-only operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-line summary is front-loaded and clear, but the Args block is padded with tautological restatements that add no information. It is short overall yet not every sentence earns its place.

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 four-parameter, zero-annotation, no-output-schema listing tool, the description should at minimum cover pagination behavior and the meaning of the enum-like 'details' level. Those gaps make it inadequate for an agent to call the tool confidently without trial and error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, but the Args block merely restates the parameter names ('Page: Page number', 'Details: Detail level') without meaning. It never explains the allowed range for details, default page size, or what a valid wallet id looks like.

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 transactions') scoped to 'a single wallet', which distinguishes it from account-wide listings. However, it does not name or contrast the closest sibling, nobitex_get_transactions_history, so an agent must guess which transaction-listing tool to use.

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 (e.g., needing a wallet id obtained elsewhere), and no mention of alternatives such as the transaction-history tool. The agent is left to infer selection criteria entirely from the 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