Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_recent_trades

Retrieve recent public trades for one Nobitex market symbol such as BTCIRT or BTCUSDT; useful for inspecting recent trading activity in that market.

Instructions

Get the most recent public trades for a single market.

Args: symbol: Market symbol such as BTCIRT or BTCUSDT ("all" is not supported).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "nobitex_get_recent_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses little beyond 'public' and 'most recent'. It does not say how many trades are returned, whether results are paginated, what fields come back, or any rate limit, all of which matter for a market-data read.

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-sentence summary followed by a single arg note, with the key constraint front-loaded and zero filler. Nothing can be trimmed without losing information.

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 one-parameter read tool with no output schema, the description covers the input well but says nothing about the shape or size of the result. An agent knows how to call it but not what to expect back.

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 compensate, and it does: it gives concrete format examples (BTCIRT, BTCUSDT) and an explicit exclusion ('all' is not supported). It stops short of stating case sensitivity, quote-currency pairing rules, or what happens with an invalid symbol.

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 and resource ('Get the most recent public trades') and scopes it to a single market. The word 'public' subtly separates it from the sibling nobitex_list_user_trades, but the difference is never made explicit.

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?

Usage is only implied: an agent can infer this is for recent market activity rather than account history. There is no explicit when-to-use, when-not-to-use, or named alternative such as nobitex_get_market_depth or nobitex_list_user_trades.

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