Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_set_anti_phishing

Create or change a Nobitex account’s anti-phishing code by submitting a new code with the one-time OTP; requires user-token authentication, not API-key auth.

Instructions

Create or change the anti-phishing code.

Args: code: New anti-phishing code. otp_code: One-time code sent to the user.

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": {
      "code": "<code>",
      "otp_code": "<otp_code>"
    },
    "name": "nobitex_set_anti_phishing"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
otp_codeYes

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, but it does disclose one genuinely useful behavioral fact: it requires a user token and API-key auth is rejected. It does not say whether an existing code is overwritten, whether this is a security-sensitive destructive action that can lock the user out, what happens if the OTP is invalid, or whether rate limits apply.

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?

It puts the operation first and then lists the arguments, which is efficient. The Args block largely restates the schema titles but adds the OTP provenance, and the trailing auth note is worth its space. A few words could be trimmed, but nothing is wasted.

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-parameter security mutation with no annotations and no output schema, the definition covers the parameters and the auth model but omits the replace-vs-create behavior, error conditions, and whether a prior OTP request is needed. It is adequate but not complete for a sensitive write endpoint.

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 all parameter meaning has to come from the description. It supplies a short gloss for each argument and usefully clarifies that otp_code is 'sent to the user.' However, it gives no format, length, or numeric/alphanumeric constraints for 'code', leaving the most important ambiguity unresolved.

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 description opens with a specific verb and resource: 'Create or change the anti-phishing code.' That is enough for an agent to separate this from the sibling reader nobitex_get_anti_phishing. It never names a sibling explicitly, so the differentiation is inferred from the set/get pairing rather than stated.

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 guidance on when to call this instead of nobitex_get_anti_phishing or any related security tool, and no exclusions or prerequisites (such as whether an OTP must be requested first or the effect this has on active withdrawals). The only contextual cue is the auth requirement, so usage is implied rather than explained.

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