Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_user_trades

Lists a user's executed Nobitex trades with filters for currency pair, trade ID, buy/sell type, order, and pagination.

Instructions

List the user's executed trades.

Args: src_currency: Source currency (must be paired with dst_currency). dst_currency: Destination currency (must be paired with src_currency). from_id: Minimum trade id. trade_type: buy or sell. trade_order: asc or desc (default desc). page: Page number. page_size: Items per page.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
from_idNo
page_sizeNo
trade_typeNo
trade_orderNo
dst_currencyNo
src_currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose one real constraint (src_currency and dst_currency must be supplied together) and a default sort direction, but says nothing about authentication being required for a user-scoped listing, pagination limits, or whether an empty result is an error versus an empty list.

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?

One summary sentence followed by a compact per-parameter list, with the purpose front-loaded and no filler. The Args entries for page and page_size are close to waste since they add nothing beyond the parameter names.

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?

Seven optional parameters, no annotations and no output schema make this a moderately complex read tool, and the description covers the parameter surface adequately but not the surrounding behavior. An agent still lacks guidance on authentication, result shape, and pagination bounds, though the absence of an output schema means return values are less obligatory to describe.

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% and the schema carries only titles, so the Args block does real work: it explains the currency pairing rule, that from_id is a minimum trade id, the buy/sell and asc/desc value sets, and the descending default. Page and page_size, however, are restated tautologically with no defaults or maximums, and the null schema defaults versus the stated "desc" default are not reconciled.

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 executed trades" gives a specific verb and resource plus a scope qualifier (the authenticated user's own trades), which separates it from public market-data siblings in spirit. It stops short of naming or contrasting with a sibling such as nobitex_get_recent_trades or nobitex_list_orders, so differentiation relies on the word "user's" alone.

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 field list: filtering by pair, id, side and paginating. There is no statement of when to prefer this over recent-trades or order-listing tools, no prerequisites, and no note that all seven parameters are optional and the call works with none of them.

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