Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_edit_position_collateral

Set the total collateral for an open margin position by specifying the position ID and new collateral amount, replacing the previous value with the exact decimal string provided.

Instructions

Set the total collateral of an open margin position.

Args: position_id: Position id. collateral: New total collateral as a decimal string (not a delta).

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": {
      "position_id": "<position_id>",
      "collateral": "<collateral>"
    },
    "name": "nobitex_edit_position_collateral"
  }
}

Input Schema

NameRequiredDescriptionDefault
collateralYes
position_idYes

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 provided, so the description carries the full behavioral burden. It correctly flags the key semantic that the value is absolute, not a delta, which matters for a financial mutation. It says nothing about permissions, whether the change is reversible, liquidation risk if collateral is lowered, or what the call returns, which is a significant gap for a write operation on a leveraged position.

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 description is short and puts the main action first, followed by an Args block that maps cleanly to the two parameters. The position_id line is redundant with the schema, but otherwise no wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutation on a margin position with no annotations and no output schema, so the description must cover safety and result behavior. It leaves out error conditions such as an invalid position or collateral below the maintenance requirement, and says nothing about what changes on success.

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 has to compensate for both parameters. It documents 'collateral' well, specifying a decimal string and that it replaces the total rather than adding to it, but 'position_id: Position id' only restates the field name. Partial compensation is worth a 3.

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: 'Set the total collateral of an open margin position.' This clearly separates it from siblings like nobitex_close_position or nobitex_get_position_status, which act on the same object differently. It never names a sibling explicitly, so it stops short of a 5.

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?

The phrase 'open margin position' hints that the position must already be open, but the description never states when an agent should adjust collateral instead of closing or reading the position. It gives no prerequisites, no mention of margin thresholds, and no alternatives.

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