Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_server_info

Reports the active Nobitex environment, base URL, and credential status so you can confirm mainnet or testnet and verify trading credentials before use.

Instructions

Report the active Nobitex environment, base URL and credential status.

Call this first to confirm whether the server is pointed at mainnet or testnet and whether trading credentials are configured.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 burden; it implies a read-only diagnostic and tells the agent what facts come back, which is useful. It does not state whether the credential status exposes sensitive values, whether the call performs any network round-trip or can fail, or how quickly it should be expected to return.

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 sentences, both load-bearing: the first declares what is returned, the second gives the sequencing instruction. The most actionable guidance ('Call this first') is easy to find and nothing is redundant.

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?

With no output schema and no annotations, the description compensates by naming the returned fields and the recommended call order. The main residual gap is failure behavior and whether the credential check is a boolean or a detailed payload, which an agent may want to know before relying on the output.

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; baseline 4 applies. The description makes clear the call is purely observational and needs no input, consistent with the empty 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 ('Report') and enumerates the exact resources returned: active environment, base URL and credential status. This clearly separates it from the many mutation-oriented siblings, though it does not name a near-neighbor such as nobitex_get_websocket_info as a contrast.

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?

Explicitly instructs 'Call this first' and gives the decision it resolves (mainnet vs testnet, credentials configured). It does not state when the call is unnecessary or name alternatives, so it falls short of full when/when-not coverage.

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