Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_emergency_cancel_code

Retrieve an emergency withdrawal-cancel code to cancel a pending Nobitex withdrawal during urgent situations.

Instructions

Get an emergency withdrawal-cancel code.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden: it does not say whether calling it generates a new code or reads an existing one, whether it has side effects such as invalidating prior codes, whether authentication is required, or whether the code expires. 'Get' implies a read, but a code-issuing operation is plausibly stateful, and the description does not resolve that ambiguity.

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?

A single short sentence with no filler. Its brevity is not wasteful in structure, though the small budget is spent on a label rather than on anything informative.

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

Completeness2/5

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

This is a zero-parameter tool, so the calling mechanics are trivial, but there is no output schema and no explanation of what the returned code is for, how long it is valid, or how it relates to nobitex_activate_emergency_cancel. For a security-sensitive emergency mechanism that is a meaningful gap.

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.

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

Purpose3/5

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

The description names a specific verb and resource (get an emergency withdrawal-cancel code), which is enough to separate it from siblings like nobitex_activate_emergency_cancel. However, 'emergency withdrawal-cancel code' is an opaque domain term — the description never says what the code is, what it protects against, or what form it takes, so the agent only learns a label, not the purpose.

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 guidance on when this should be retrieved, whether it precedes or follows nobitex_activate_emergency_cancel, or whether it can be fetched repeatedly. The agent must infer the workflow entirely.

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