Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_margin_delegation_limit

Retrieves the margin delegation limit for a specified Nobitex market symbol, helping you check available delegation before margin trading.

Instructions

Get the delegation limit for a margin market.

Args: market: Market symbol, e.g. "BTCIRT".

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": {
      "market": "<market>"
    },
    "name": "nobitex_get_margin_delegation_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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. The verb "Get" implies a read-only call, but the description does not say whether authentication is needed beyond a token, whether the limit is per-market or account-wide, what units or currency the limit is expressed in, or what shape the response takes.

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?

Two short lines with no filler; the purpose sentence is front-loaded and the parameter example follows immediately. The Args block formatting is slightly formal for a single parameter but costs nothing in clarity.

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, this is minimally viable: the agent knows what to pass and roughly what to ask for. However, the domain term "delegation limit" is never defined, and with no output schema the description should at least hint at whether the return is a numeric amount, a currency, or a structured object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 for the single parameter. It does add a concrete example format ("BTCIRT"), which conveys the symbol convention beyond the bare `string` type in the schema, but it does not clarify case sensitivity, quote-currency pairing rules, or valid symbol sources.

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 delegation limit for a margin market." The resource is unambiguous and clearly distinct from sibling tools like nobitex_place_margin_order or nobitex_list_margin_markets, though it does not explicitly name an alternative or contrast with one.

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 use this tool versus alternatives, no prerequisites (e.g., whether a margin account or prior market lookup is required), and no stated conditions or exclusions. The agent must infer all of this from the tool name alone.

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