Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_margin_markets

List available margin markets on Nobitex, optionally including extra market details such as delegation limits, so traders can identify which assets support margin trading.

Instructions

List margin markets.

Args: details: Include extra market details such as delegation 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_list_margin_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsNo

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 largely drops it. It does not say whether this is a public/unauthenticated endpoint, whether results are cached or paginated, or what the response contains; only the optional 'details' flag is explained.

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?

Extremely short and front-loaded, with the purpose stated in the first line and the parameter note immediately after. The 'Args:' docstring framing is minor boilerplate but nothing is wasted.

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 single-parameter list tool with no output schema, the description covers the basics but omits what a caller would want: the shape of a market entry, whether authentication is required, and whether results are stable reference data. Adequate but with clear gaps.

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 description coverage is 0%, so the description must compensate, and it does: the single 'details' parameter is explained as pulling extra market data such as delegation limits, which adds real meaning beyond a bare boolean. It could still note the default behavior, but the one parameter is otherwise covered.

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?

The description gives a specific verb and resource ('List margin markets'), so the agent knows exactly what the call returns conceptually. It does not distinguish itself from siblings such as nobitex_list_orders or nobitex_get_margin_delegation_limit, leaving that differentiation to the name alone.

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 to call this versus the margin-related siblings, nor any prerequisites or exclusions. The description only states the resource, leaving the agent to infer that this is a reference-data lookup.

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