Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_set_leverage

Set leverage for a trading position on OKX. Specify instrument ID, leverage multiple, and margin mode to adjust risk.

Instructions

[L:WRITE] CAT:[账户] | → 请先调用 agent_catalog

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": {
      "instId": "<instId>",
      "lever": "<lever>",
      "mgnMode": "<mgnMode>"
    },
    "name": "okx_set_leverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
leverYes杠杆倍数，如 10。必须在仓位档位允许范围内
instIdYes产品ID，如 BTC-USDT-SWAP。必填
mgnModeYes保证金模式。cross=全仓, isolated=逐仓
posSideNo持仓方向。不填则双向生效

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

D1.6/5.0
Behavior1/5

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

No annotations provided, and the description lacks behavioral details. It hints at a write operation via "L:WRITE" but does not explain side effects, permission requirements, or what changes occur. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but incomplete and uninformative. It is under-specified rather than concise, providing no useful information for selection or invocation.

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

Completeness1/5

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

The tool is a mutating operation (set leverage) with potential risks, yet the description omits crucial context like required prerequisites beyond a generic reference, risk warnings, or relation to other tools. Without annotations or output schema, the description is completely inadequate.

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?

The input schema has 100% coverage with descriptions and enums for all parameters. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does not state what the tool does; it only contains a cryptic label "L:WRITE" and a prerequisite to call another tool. The name suggests setting leverage, but the description fails to confirm or detail the action.

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?

No guidance on when to use this tool versus alternatives. The only hint is a prerequisite ('请先调用 agent_catalog'), but no context about use cases or exclusions.

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