Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_batch_orders

Execute multiple OKX exchange orders in one batch. Accepts up to 20 orders in JSON format for efficient trading.

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": {
      "orders": "<orders>"
    },
    "name": "okx_batch_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
ordersYes订单数组JSON字符串，如 '[{"instId":"BTC-USDT","tdMode":"cash","side":"buy","ordType":"limit","sz":"0.001","px":"60000"}]'。最多20笔

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations provided, the description must disclose behavioral traits. It fails to mention that the tool submits multiple orders, any side effects, required permissions, or rate limits. The cryptic label does not convey meaningful behavioral information.

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 very short but at the expense of clarity. It is under-specified and does not explain the tool's purpose, making it not appropriately sized for the complexity of a batch order tool.

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's complexity (batch orders), the description is severely lacking. It omits return values, error handling, and operational context, making it incomplete for an AI agent to use effectively.

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 schema has 100% description coverage for the single parameter 'orders', including format and max count. The description adds no 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.

Purpose2/5

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

The description '[L:WRITE] CAT:[交易] | → 请先调用 agent_catalog' is cryptic and does not clearly state that this tool places multiple orders. It hints at a write operation and a category, but fails to specify the primary function of batch order placement, making it hard to distinguish from sibling tools like okx_place_order.

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 is provided on when to use this tool versus alternatives such as okx_place_order or okx_batch_cancel_orders. The only directive is to call agent_catalog first, which is a prerequisite step but does not help with tool selection.

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