Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_market_stats

Fetch 24-hour price, volume, and change statistics for one or more Nobitex markets to track current performance and compare trading pairs.

Instructions

Get 24h market statistics (price, volume, change) for markets.

Args: src_currency: Source currency or comma-separated list, e.g. "btc,eth". dst_currency: Destination currency or comma-separated list, e.g. "rls,usdt".

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

Input Schema

NameRequiredDescriptionDefault
dst_currencyNo
src_currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never states that this is a read-only query, whether results are rate limited, or — critically — what happens when both optional filters are omitted (all markets? empty result?), which is the main behavioral unknown for this tool.

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?

The purpose sentence is front-loaded and the args block is tight and example-driven, with no filler. The docstring formatting is slightly redundant with the prose but costs almost nothing.

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 simple two-optional-parameter read tool with no output schema, the description covers inputs well but leaves the default-scope behavior and return shape (single object vs. mapping per market) undefined. Adequate, but an agent cannot fully predict the response without calling it.

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?

Schema coverage is 0%, so the description must carry parameter meaning and it largely does: it explains that both arguments accept a single currency or a comma-separated list, with concrete examples ('btc,eth', 'rls,usdt'). It does not explain the null default or the effect of omitting a filter, which keeps it short of a 5.

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?

Names a specific verb and resource ('Get 24h market statistics') and enumerates the returned fields (price, volume, change), which distinguishes it from siblings like get_ohlc_history or get_orderbook. It stops short of explicitly naming which sibling to use for historical or order-book data, so it is clear but not sibling-differentiating.

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 or when-not-to-use guidance, and no alternative is named. An agent must infer from '24h' alone that this is a snapshot rather than a time series, and gets no signal about choosing between this and the OHLC or order-book tools.

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