Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_grid_sub_orders

Retrieve filled or unfilled sub-orders from a grid strategy using the algo ID and grid 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": {
      "algoId": "<algoId>",
      "algoOrdType": "<algoOrdType>",
      "type": "<type>"
    },
    "name": "okx_get_grid_sub_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesfilled=已成交，unfilled=未成交
algoIdYes网格策略ID
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 are provided. The description only hints at a read operation via '[L:READ]' but does not disclose important behavioral traits such as pagination, rate limits, or any side effects. The lack of output schema further reduces transparency.

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 (one line) but fails to convey essential information. Conciseness should not come at the cost of clarity. The cryptic prefix and lack of complete sentences make it poorly structured.

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?

Given the absence of an output schema and the tool's moderate complexity (3 required params), the description is incomplete. It does not explain what the tool returns, the result format, or when it should be used. Significant gaps remain.

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% and each parameter has a description in the input schema (though in Chinese). The tool description does not add additional meaning beyond what the schema provides, which is acceptable given 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?

The description is cryptic ('[L:READ] CAT:[策略-网格]') and does not explicitly state what the tool does. The name suggests retrieving grid sub-orders, but the description lacks a clear verb+resource. It relies on abbreviations and Chinese without explaining the operation.

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 precondition ('请先调用 agent_catalog'), but no guidance on when to use this tool versus sibling tools like okx_get_grid_orders_pending or okx_get_grid_orders_history. No rationale for selection is given.

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