Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_request

Call any Nobitex API path with correct authentication and signing to use documented endpoints that lack a dedicated tool.

Instructions

Call any Nobitex API path with correct authentication and signing.

Use this for documented endpoints that do not yet have a dedicated tool, for example /v2/otp/request, /users/wallets/convert, /credit/*, /market/orders/batch-add, /market/orders/cancel-batch, /users/preferences.

Args: method: HTTP method. path: API path beginning with "/", e.g. "/v2/otp/request". params: Query parameters. body: JSON request body. auth: "auto" (use configured credentials), "none", "token" or "key". totp: Optional X-TOTP code.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "nobitex_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
authNoauto
bodyNo
pathYes
totpNo
methodYes
paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose a real behavioral trait beyond the schema — that signing is handled automatically and that auth mode can be selected — but it never warns that method values include POST/PUT/DELETE/PATCH, i.e. that this tool can perform irreversible mutations (order cancellation, withdrawals) with no dry-run or confirmation semantics described. Nothing about error format, rate limits, or what signing failures look like is disclosed.

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?

Front-loaded purpose, then a scoping sentence, then a compact Args list where each entry earns its place. The example-path enumeration is the most valuable part and is kept short. The 'Args:' docstring formatting is slightly boilerplate but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a generic passthrough with six parameters, no output schema, and no annotations, the description does the essential job: purpose, when to reach for it, and the meaning of every parameter. The remaining gap is behavioral risk on mutating methods and any hint about response or error shape, which matters more here than for a narrow single-endpoint tool.

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 Args block is the only documentation and it covers all six parameters. It adds genuine meaning beyond the bare schema: path must begin with '/', params are query parameters versus body as the JSON request body, auth modes are glossed ('auto' = use configured credentials; 'none', 'token', 'key'), and totp is identified as an X-TOTP header code. It is weaker on 'token' vs 'key' and on whether body is required for POST.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line states a specific verb and resource: 'Call any Nobitex API path with correct authentication and signing.' The second line explicitly scopes it as the escape hatch for 'documented endpoints that do not yet have a dedicated tool', which is exactly the distinction an agent needs against siblings like nobitex_cancel_order or nobitex_add_bank_card.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The condition 'endpoints that do not yet have a dedicated tool' functions as an implicit exclusion rule, and six concrete example paths (/v2/otp/request, /users/wallets/convert, /credit/*, etc.) show the intended shape of use. It stops short of stating the inverse explicitly ('prefer the dedicated tool when one exists') or naming any precondition such as API key scope, so it is strong but not fully closed.

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