Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_transactions_history

Retrieve a user's transaction history across wallets, filtered by currency, transaction type, date range, ID, and pagination, with optional detailed or downloadable exports.

Instructions

Get the user's transaction history across wallets.

Args: currency: Optional currency filter. tp: Transaction type list (API-specific string). from_ts: Start time as Unix timestamp (seconds). to_ts: End time as Unix timestamp (seconds). from_id: Minimum transaction id. page: Page number. page_size: Items per page. details: Detail level. download: Request a downloadable export when supported.

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

Input Schema

NameRequiredDescriptionDefault
tpNo
pageNo
to_tsNo
detailsNo
from_idNo
from_tsNo
currencyNo
downloadNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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, yet it says nothing about authentication/API-key requirements, rate limits, result ordering, whether the response is paginated with a total count, or what the download mode actually produces. The implication that it is a read-only history lookup is the only behavioral signal, and it is never stated explicitly.

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 purpose sentence is front-loaded and efficient, but the Args block mostly restates schema property names with thin glosses, and a few entries ('Detail level', 'API-specific string') spend words without resolving anything. It is not bloated, but several lines do not earn their place beyond what the schema already shows.

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?

This is a 9-parameter, fully optional-argument tool with no annotations and no output schema, so the description must explain return shape, pagination semantics, and defaults. It supplies none of those, leaving an agent unsure how to page through results or what download mode returns.

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 doing real work: it clarifies from_ts/to_ts are Unix seconds (valuable, since milliseconds are a common alternative), that from_id is a minimum transaction id rather than a starting offset, and that currency is an optional filter. However, 'tp: Transaction type list (API-specific string)' conflicts with the schema's plain string type, and 'details: Detail level' and 'download' remain vague about accepted values.

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?

The opening sentence gives a specific verb and resource: fetching the user's transaction history scoped 'across wallets'. That is clear enough to distinguish it from wallet-balance or profit tools, but it does not address the very similar-looking sibling nobitex_list_wallet_transactions, leaving genuine ambiguity about which one retrieves transactions.

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 use this tool versus alternatives, no preconditions, and no note on how pagination (page/page_size) interacts with from_id. The only contextual hint is 'download: Request a downloadable export when supported', which is about a parameter rather than about tool selection.

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