Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_paper_reset

Resets paper-trading balances, orders, trades, and positions to restart a clean simulated Nobitex trading session when the server runs in dry-run mode.

Instructions

Reset paper-trading balances, orders, trades and positions.

Only available when the server runs with NOBITEX_DRY_RUN=true.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does convey that this is a destructive, environment-gated operation, but it does not say whether the reset is to zero or to configured initial balances, whether it can be undone, or what the call returns on success versus failure.

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, front-loaded with the action and affected resources, then the availability constraint. No filler or redundant 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?

For a zero-parameter tool with no output schema and no annotations, the definition covers what is reset and when it is callable. The main remaining gap is the post-reset state and irreversibility, which matters because the action destroys balances, orders, trades and positions.

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 is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the reset is global with no scoping arguments.

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 ("Reset") and enumerates exactly what is affected: paper-trading balances, orders, trades and positions. The "paper-trading" qualifier immediately separates it from real-account mutation siblings such as nobitex_cancel_order or nobitex_close_position.

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 hard precondition (only available when NOBITEX_DRY_RUN=true), which is genuinely useful for deciding whether calling it can work at all. It does not say when an agent should want to reset — e.g. before starting a fresh simulation run — nor what happens if invoked in live mode, so usage is only partially guided.

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