Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_legacy_login

Authenticate to Nobitex through the legacy login endpoint using username and password, with optional captcha and persistent token support for bot or session access.

Instructions

Log in through the legacy endpoint.

Args: username: Username/email. password: Password. captcha: Captcha value; "api" for bots. remember: "yes" to issue a persistent token.

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>",
      "password": "<password>"
    },
    "name": "nobitex_legacy_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
captchaNoapi
passwordYes
rememberNo
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 two useful behaviors: captcha 'api' is the bot bypass, and remember='yes' issues a persistent token. It omits what happens to the session on failure, token lifetime/revocation, and any rate limiting or credential-handling concerns.

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 docstring format is compact and front-loads the purpose before the argument list. Every line carries parameter meaning with no padding, though the argument list is bare-bones rather than structured.

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 security-sensitive authentication tool with no annotations and no output schema, the definition should say something about what the call returns (token/session), whether it is idempotent, and how it relates to nobitex_login. The parameter semantics are adequate but the operational context is thin.

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 largely does: it clarifies username is a username/email, that captcha accepts the special value 'api' for bots, and that remember must be exactly 'yes' to get a persistent token. Only the password parameter is left as self-evident.

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 through the legacy endpoint'), so an agent knows exactly what operation this performs. However, 'legacy' is never contrasted with the sibling nobitex_login, leaving the distinction between the two login tools unexplained.

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 guidance on when to use this legacy endpoint versus nobitex_login, which appears in the sibling list. The word 'legacy' hints at an alternative path but no condition, prerequisite, or exclusion is stated.

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