Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_positions

Retrieves margin positions from Nobitex, filtered by base/quote currency and active or past status, with pagination for reviewing open and settled positions.

Instructions

List margin positions.

Args: src_currency: Base currency filter. dst_currency: Quote currency filter. status: "active" (open) or "past" (settled/closed/liquidated). 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_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
statusNo
page_sizeNo
dst_currencyNo
src_currencyNo

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?

With no annotations supplied, the description carries the full behavioral burden and largely does not meet it. "List" implies a read, but authentication requirements, rate limits, pagination defaults, and what a position record contains are all unstated; only the status semantics add real behavioral color.

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 purpose statement is front-loaded in a single line, followed by a compact per-argument list with no filler prose. The docstring-style Args block is slightly redundant with the schema property names but stays short and scannable.

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 read-only list tool with zero annotations and no output schema, the definition covers filters and pagination at a surface level but omits return shape, sort order, and total-count behavior. It is minimally adequate to invoke the tool, not enough to predict what comes back.

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, and it does document all five parameters at a basic level. The clearest value-add is decoding "active" as open and "past" as settled/closed/liquidated; however, currency filter format (symbol vs. ticker casing), page numbering base, and page_size limits or defaults are left unspecified.

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 margin positions" gives a specific verb and resource, so the agent immediately knows this is a filtered enumeration of margin positions. It does not, however, contrast with nearby siblings such as nobitex_list_margin_markets or nobitex_list_orders, so the agent must infer the boundary itself.

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, and no named alternative for related listing tasks. The status values hint at two distinct use cases (open vs. settled positions), but the description never says when to pick one over the other.

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