Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_resend_login_otp

Resends the MFA one-time password for a pending Nobitex login using the username, temporary MFA token, and device ID from the first step.

Instructions

Resend the MFA OTP for a pending login.

Args: username: Username/email. mfa_token: Temporary token from the first step. device: Device id from the first step.

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>",
      "mfa_token": "<mfa_token>",
      "device": "<device>"
    },
    "name": "nobitex_resend_login_otp"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYes
usernameYes
mfa_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say whether resending invalidates the previous OTP, which channel the OTP is delivered on, whether rate limiting or lockout applies to repeated resends, or what a success/failure response looks like — all material for an auth-adjacent mutation.

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?

One front-loaded sentence states the action, followed by a compact Args block that earns its place given the 0% schema coverage. No filler, though the raw docstring-style formatting is slightly less scannable than prose.

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 three-required-parameter, no-annotation, no-output-schema auth tool, the description covers what the tool does and where the inputs come from, but omits OTP lifecycle behavior (expiry, invalidation, delivery channel, throttling) that an agent needs to call it correctly and recover from errors.

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% (titles only), so the description must compensate, and it does partially: username is 'Username/email' (clarifying it accepts either), and mfa_token/device are identified as values from the first step, which is genuinely non-obvious. It still gives no format or provenance detail for 'device' (id type, how it's obtained beyond 'first step').

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 — 'Resend the MFA OTP' — and scopes it to 'a pending login', which distinguishes it from the siblings nobitex_login and nobitex_legacy_login that presumably initiate the flow. It stops short of naming those siblings explicitly, so it earns a 4 rather than 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?

Usage is implied rather than stated: 'for a pending login' plus 'Temporary token from the first step' and 'Device id from the first step' tells the agent this is a mid-flow recovery step for an OTP that didn't arrive. There is no explicit when-not guidance (e.g., what to do if the first step returned no mfa_token) and no mention of an alternative tool.

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