Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_login_attempts

Retrieves a Nobitex user's login attempt history for security review. Requires a user token, since API-key authentication is not accepted for this endpoint.

Instructions

Get the user's login attempt history.

Requires a user token; Nobitex does not accept API-key auth for this endpoint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nobitex_get_login_attempts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden and it does disclose one important non-obvious trait: API-key auth is rejected and a user token is mandatory, which prevents a predictable auth failure. It says nothing about pagination, time range of results, rate limits, or how many attempts are returned — meaningful gaps for a history-listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, purpose first and the auth constraint second. Every sentence earns its place and there is no filler or repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read call with no output schema, an agent mainly needs to know what it retrieves and what auth it needs — both are covered. The missing piece is any hint about the return shape or result volume (attempt count, time window, pagination), which the agent must discover by calling it.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline of 4 applies. Nothing in the description conflicts with the empty input schema.

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: 'Get the user's login attempt history.' That clearly separates it from sibling login-flow tools like nobitex_login, nobitex_legacy_login, and nobitex_resend_login_otp, which act on authentication rather than reporting on it. It stops short of explicitly naming an alternative, so it is a strong 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?

The description gives a precondition (a user token is required) but no when-to-use or when-not-to-use guidance relative to the login siblings. An agent can infer this is a reporting call, but the definition never says so directly or rules out an alternative path for the same information.

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