Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_set_position_mode

Set your OKX account position mode to long_short_mode or net_mode to control how positions are opened and managed.

Instructions

[L:ADMIN] 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": {
      "posMode": "<posMode>"
    },
    "name": "okx_set_position_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
posModeYes持仓模式。long_short_mode=双向持仓, net_mode=单向持仓

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

D1.4/5.0
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It only mentions a prerequisite call, not what the tool does, whether it is destructive, requires authentication, or has side effects.

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?

Extremely short but not concise in a helpful way. It is cryptic and fails to communicate tool function, thus does not earn its place.

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?

Given the tool modifies account settings, lacks output schema, and has no annotations, the description is completely inadequate. No mention of return values, side effects, or prerequisites beyond the vague agent_catalog call.

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 coverage is 100% with a description for posMode. The tool description adds no semantic value 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 '[L:ADMIN] CAT:[账户] | → 请先调用 agent_catalog' provides metadata and a directive but does not state the tool's purpose. The name implies setting position mode, but the description fails to confirm this.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 like okx_set_account_mode. The instruction to call agent_catalog first is a prerequisite, not usage context.

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