Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_create_grid_order

Create grid trading orders on OKX with customizable price range and grid count. Supports spot, contract, and moon grid types.

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>",
      "algoOrdType": "<algoOrdType>",
      "maxPx": "<maxPx>",
      "minPx": "<minPx>",
      "gridNum": "<gridNum>"
    },
    "name": "okx_create_grid_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxPxYes价格上限。必填
minPxYes价格下限。必填
instIdYes产品ID。必填
gridNumYes网格数量。必填
directionNo合约网格方向。long=做多, short=做空, neutral=中性
algoOrdTypeYes网格类型。grid=现货网格, contract_grid=合约网格, moon_grid=天地网格

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. The only hint is '[L:WRITE]', which suggests a write operation, but it doesn't explain what exactly is written (e.g., order placement, account modification) or any side effects, permissions needed, or rate limits. The description is insufficient for an agent to understand the tool's behavior.

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 this is not effective conciseness. It omits essential information about the tool's purpose and usage. Every sentence should earn its place, but here the two fragments are insufficient to guide an agent, lacking clear structure or completeness.

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 has 6 parameters (5 required) and no output schema, the description must explain the tool's function, parameter relations, and return value. It fails to do so. The directive to call agent_catalog is a small step, but overall the description is completely inadequate for an agent to invoke this tool correctly.

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% description coverage for all parameters, providing clear meanings (e.g., price range, grid number, direction enums). The tool description adds no additional semantic value beyond what the schema already provides, so a baseline score of 3 is appropriate.

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

Purpose2/5

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

The description does not clearly state what the tool does. It contains a category tag '[策略-网格]' (strategy-grid) and a directive to call agent_catalog first, but no verb like 'create' or 'place'. The purpose is only vaguely implied by the category and the tool name.

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 description only provides a single usage instruction: '请先调用 agent_catalog' (call agent_catalog first). It does not specify when to use this tool versus the many sibling tools, nor does it describe any preconditions or alternatives beyond the prerequisite.

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