Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_logout

Logs out the current Nobitex user token to terminate an authenticated session; requires a user token, as API-key authentication is not accepted for this endpoint.

Instructions

Log out the current user token.

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_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does add real value by disclosing the auth constraint that Nobitex rejects API-key auth here, which is exactly the kind of non-obvious behavior a schema cannot express. However, it never says whether the token is invalidated server-side or only locally, whether the action is reversible, or what a failed logout returns, so a caller cannot predict consequences.

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, with the action first and the auth constraint second. Every sentence adds information and there is no padding or restatement 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?

The tool is simple, parameter-free, has no output schema, and its one non-obvious requirement, the auth type, is stated explicitly. The remaining gap is post-condition behavior, that is, whether the session is destroyed server-side, which leaves an agent slightly uncertain about how to verify success. Beyond that the definition is proportionate to the tool's complexity.

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 nothing for the description to disambiguate, which is the baseline-4 case. The mention of 'the current user token' implicitly clarifies that the token is supplied by the session rather than as an argument, which is a helpful clarification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Log out the current user token.' This is unambiguous and clearly distinct from every sibling in the catalog, none of which is a session-termination tool. No sibling differentiation is needed because there is no plausible confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete prerequisite for use: a user token, and explicitly rules out API-key auth for this endpoint. That is valuable when-to-use context an agent cannot infer. It stops short of a 5 because it names no alternatives (e.g., what to use instead if only an API key is available) and no edge cases such as what to do with an already-expired token.

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