Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_limitations

Retrieve Nobitex account limitations and verification limits to determine available trading and withdrawal capacities before placing orders.

Instructions

Get the user's account limitations and verification limits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; 'Get' does signal a non-mutating read. However, it says nothing about authentication/API-key requirements, whether limits are tier-dependent on KYC level, or whether the call can fail for unverified accounts.

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?

One front-loaded sentence with no filler; the pairing of 'account limitations' and 'verification limits' signals the two categories of data returned without padding.

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 zero-parameter read with no annotations and no output schema, the description should at least sketch what comes back (e.g., withdrawal/deposit caps, verification tier) or under what conditions it is useful. It leaves the agent guessing about the return content, though the risk from a simple read is low.

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 and the schema has none to document, so there is no semantic gap to fill. Baseline 4 applies for a parameterless call.

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 ('Get') and resource ('the user's account limitations and verification limits'), which is enough to distinguish it from most siblings such as get_wallet_balance or get_profile. It does not explicitly differentiate itself from the nearby get_margin_delegation_limit, which an agent could plausibly confuse with 'limitations'.

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 when-to-use guidance, no prerequisite or exclusion, and no named alternative. The agent must infer that this is the pre-flight check before trading or withdrawing, and cannot tell how it relates to the margin delegation limit 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