Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_login

Log in with credentials and captcha to obtain a user token, including MFA verification, for authenticated exchange operations.

Instructions

Log in and obtain a user token (handles MFA second step).

Args: username: Username/email. password: Password (first step). captcha: Captcha value; "api" for bots. remember: "yes" to issue a persistent token. mfa_token: Temporary token from the first step (MFA step). device: Device id from the first step (MFA step). otp: OTP for MFA methods 3/4.

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": {
      "username": "<username>"
    },
    "name": "nobitex_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
otpNo
deviceNo
captchaNoapi
passwordNo
rememberNo
usernameYes
mfa_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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. It usefully discloses the MFA second-step flow, persistent token behavior via remember="yes", and captcha="api" for bots, but it does not describe failure behavior, token lifetime, rate limits, or security implications.

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 first sentence is front-loaded with purpose and MFA scope, and the Args list is structured and efficient for a seven-parameter tool. There is little wasted wording, though the raw Args formatting is functional rather than polished.

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 login tool with MFA and no output schema, the description covers purpose and parameters but omits return-value details such as token format and failure/error behavior. It is adequate but not fully self-sufficient for an agent invoking the 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 description must compensate, and it does: it documents all seven parameters, including username/email, password as first step, captcha="api" for bots, remember="yes" for a persistent token, and the MFA-specific roles of mfa_token, device, and otp. It could still clarify MFA methods 3/4 and device format, but the coverage is strong.

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 states a specific verb and resource: "Log in and obtain a user token," and adds scope with "handles MFA second step." It does not explicitly distinguish this from sibling login tools such as nobitex_legacy_login, so it falls short of a 5.

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 description implies usage by noting the first step versus the MFA step and by labeling mfa_token and device as coming from the first step. However, it gives no explicit guidance on when to use this tool versus nobitex_legacy_login or nobitex_resend_login_otp.

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