Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_delete_api_key

Delete a Nobitex API key by providing its public key and TOTP code; requires a user token because API-key auth is not accepted.

Instructions

Delete an API key.

Args: public_key: Public key of the API key. 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": {
      "public_key": "<public_key>"
    },
    "name": "nobitex_delete_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
totpNo
public_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 burden, and it does disclose one important behavior beyond the schema: deletion requires a user token because Nobitex rejects API-key auth on this endpoint. However, it never says deletion is irreversible, whether it revokes live sessions or open orders, or what a success or error response looks like.

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 operation statement is front-loaded in a single short sentence, followed by a compact args block; there is no filler. The auth note sits after the args rather than with the operation, which is a minor ordering weakness.

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 two-param destructive tool with no annotations and no output schema, the definition covers identity, params, and auth. It still omits irreversibility, side effects on active sessions, and the required/optional mismatch with the schema for totp.

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 description must compensate, and it does document both params (public_key meaning, totp sent as X-TOTP header). However, it calls totp "required" while the schema declares only public_key required and totp nullable with a default, which could mislead an agent into believing the call fails without a TOTP.

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: "Delete an API key." This unambiguously distinguishes it from the create/update/list siblings. It does not explicitly name those alternatives, but no agent could confuse the operation.

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 explicit when-to-use guidance: nothing about when to delete versus deactivate/update a key, and no warning about revocation side effects. The only contextual clue is the auth requirement, which is a constraint, not usage guidance.

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