Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_recurring_sub_orders

Retrieve sub-orders for a recurring investment plan on OKX by providing the plan ID.

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>"
    },
    "name": "okx_get_recurring_sub_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数，默认100
algoIdYes定投计划ID。必填

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.5/5.0
Behavior2/5

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

No annotations provided; description only includes the '[L:READ]' tag, hinting at read-only behavior. No disclosure of destructive potential, authorization needs, or side effects. Minimal behavioral context beyond the tag.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is extremely short, but no wasted words. However, it is under-specified for the tool's complexity, failing to convey essential information. Acceptable conciseness but at the cost of completeness.

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?

With no output schema, no annotations, and only 2 parameters, the description lacks completeness. It does not explain return values, pagination, or typical use context. The prerequisite to call agent_catalog is helpful but insufficient.

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 parameter descriptions in the schema. Description adds no parameter-level information; baseline 3 is appropriate as schema already documents parameters.

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

Purpose3/5

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

Description includes '[L:READ]' indicating a read operation, but does not explicitly state the verb or resource. The name 'get_recurring_sub_orders' provides purpose, but the description adds little clarity. It vaguely categorizes as '策略-网格' (Strategy-Grid) without differentiation from siblings.

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 instructs to 'call agent_catalog first', which is a prerequisite but not usage guidance. No information on when to use this tool versus alternatives, no exclusions or context for decision-making.

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