Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_create_api_key

Generate a Nobitex API key with permissions, optional IP whitelist and expiry; the private key is returned once. Requires a user token and TOTP code.

Instructions

Create an API key. The private key is returned only once.

Args: name: Key name. permissions: Comma-separated permissions: READ,TRADE,WITHDRAW,DEPOSIT,ADDRESS_BOOK,OTP,VIP_CREDIT. description: Optional description. ip_whitelist: Optional list of allowed IPv4/IPv6 addresses (max 15). expiration_date: Optional ISO-8601 expiry in the future. totp: TOTP two-factor code (required, sent as X-TOTP).

Requires a user token; Nobitex does not accept API-key auth for this endpoint.

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": {
      "name": "<name>",
      "permissions": "<permissions>"
    },
    "name": "nobitex_create_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
totpNo
descriptionNo
permissionsYes
ip_whitelistNo
expiration_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose three important traits: the private key is shown only once, user-token auth is mandatory, and TOTP is transmitted as the X-TOTP header. It stops short of describing what the response contains, whether the key is active immediately, error conditions, or how to rotate or revoke it afterwards.

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 behavioral facts and the one-time secret disclosure are front-loaded in two short sentences, followed by a disciplined Args block with no filler. The structure is serviceable rather than elegant, but every line carries information an agent needs.

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 high-stakes credential-creation tool with zero annotation coverage and no output schema, the definition covers auth requirements, secret handling, TOTP transmission, and all parameter constraints. The remaining gap is the return shape, since without an output schema the agent cannot know the field name holding the private key.

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

Parameters5/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 entirely, and it does: it enumerates the full permission vocabulary (READ, TRADE, WITHDRAW, DEPOSIT, ADDRESS_BOOK, OTP, VIP_CREDIT), states the comma-separated format, caps ip_whitelist at 15 IPv4/IPv6 addresses, and requires an ISO-8601 expiry in the future. This is meaning the schema alone cannot convey and it is the most safety-critical information in the definition.

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 ("Create an API key") and immediately adds the key distinguishing behavior that the private key is returned only once. It does not explicitly contrast itself with nobitex_update_api_key or nobitex_list_api_keys, so it falls short of full sibling differentiation, but the operation is unmistakable.

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?

The closing note that a user token is required and that API-key auth is rejected for this endpoint is a genuine prerequisite, which is more than many definitions offer. However, there is no statement of when to create a new key versus updating an existing one, nor any warning about the irreversibility of minting withdrawal-capable credentials.

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