Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_create_recurring_plan

Create a recurring investment plan on OKX by specifying the product, currency, amount, and period (daily, weekly, or monthly).

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>",
      "currency": "<currency>",
      "amount": "<amount>",
      "period": "<period>"
    },
    "name": "okx_create_recurring_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes每期投资数量。必填
instIdYes定投产品ID。必填
periodYes定投周期。daily=每日, weekly=每周, monthly=每月
currencyYes定投资金币种。必填

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?

The description includes '[L:WRITE]' hinting at a write operation, but no annotations exist. It does not explain effects, permissions, or rate limits, leaving major behavioral gaps.

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?

Extremely short but underspecified; not concise in a helpful way. Lacks structure and important information.

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?

With 4 required parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain the tool's purpose, behavior, or prerequisites beyond a vague label.

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 all parameters are clearly described in the input schema. The description adds no additional meaning, 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 is a label ('策略-网格') and a prerequisite instruction ('请先调用 agent_catalog'), but it does not state what the tool does. The purpose is only inferred from the tool name and schema.

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?

No guidance on when to use this tool versus alternatives. Only a prerequisite instruction to call agent_catalog first, which is minimal context.

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