Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_grid_orders_pending

Retrieve pending grid orders with filters for product ID, instrument type, or grid strategy type.

Instructions

[L:READ] 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": {
      "algoOrdType": "<algoOrdType>"
    },
    "name": "okx_get_grid_orders_pending"
  }
}

Input Schema

NameRequiredDescriptionDefault
instIdNo产品ID，不填返回全部
instTypeNo产品类型筛选
algoOrdTypeYes网格类型

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. '[L:READ]' suggests read-only, but this is self-declared and not validated. No mention of side effects, rate limits, or other behavioral traits beyond the read hint.

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?

Very short but unnecessarily cryptic with brackets and Chinese. The directive to call agent_catalog first is useful but the format is poor; not front-loaded with clear purpose.

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?

No output schema and the domain (grid orders) is complex. Description lacks explanation of what is returned (e.g., list of pending orders, fields). The tool seems to require a prerequisite but does not complete the picture for an AI agent.

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 100%, so the schema already describes all three parameters. The description adds no additional meaning beyond what is in the schema, meeting the baseline for high coverage.

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?

Description uses cryptic prefixes '[L:READ] CAT:[策略-网格]' and Chinese directive instead of a clear English statement. The tool name suggests 'get pending grid orders' but the description does not explicitly confirm this. Distinguishing from sibling grid order tools (e.g., okx_get_grid_orders_history) is not addressed.

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?

Only guidance is '→ 请先调用 agent_catalog', which is a prerequisite but does not explain when to use this tool versus alternatives like okx_get_grid_orders_history or okx_get_grid_sub_orders. No context on when not to use.

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