Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_update_api_key

Update an API key's name, description, or IP whitelist with TOTP verification and user-token authentication.

Instructions

Update an API key's name, description or IP whitelist.

Args: public_key: Public key of the API key. totp: TOTP two-factor code (required, sent as X-TOTP). name: New name. description: New description. ip_whitelist: New IP whitelist (max 15).

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

Input Schema

NameRequiredDescriptionDefault
nameNo
totpNo
public_keyYes
descriptionNo
ip_whitelistNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 load, and it does add real value: it declares that a user token is required, that API-key auth will not work on this endpoint, and that totp is transmitted as an X-TOTP header. It omits partial-update semantics — notably whether passing null for name/description/ip_whitelist clears the field or leaves it unchanged, which matters given all are defaulted to null — and says nothing about the response or whether changes are reversible.

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 one-line summary is correctly front-loaded, and the auth caveat is placed last where it is easy to catch. The Args block duplicates schema titles somewhat, but it is scannable and short overall.

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 5-parameter mutation with no annotations, no output schema, and 0% schema coverage, the definition covers auth mechanics well but leaves a meaningful hole around optional-field semantics (null versus omitted). An agent could call it correctly for the required public_key but would be guessing about how to leave fields untouched.

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. It does list all five parameters with brief glosses and adds two facts not in the schema: the totp header name and the max-15 cap on ip_whitelist. However, the remaining arg notes ("New name", "New description", "Public key of the API key") largely restate the schema titles, and null/reset behavior is still unexplained.

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?

The first sentence uses a specific verb+resource ("Update an API key's name, description or IP whitelist"), which is unambiguous and distinguishable from the create/delete/list siblings. It stops short of naming those siblings explicitly, but the operation is clear.

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 implied by the operation type: it applies to an existing key identified by public_key. There is no explicit guidance on when to choose this over nobitex_create_api_key or nobitex_delete_api_key, and no statement about which fields may be changed independently.

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