hvip MCP Server

okx_indicator_batch

Batch calculate technical indicators like SMA, RSI, MACD for any OKX instrument. Select bar size and multiple indicators to retrieve combined market data in one call.

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": {
      "instId": "<instId>",
      "indicators": "<indicators>"
    },
    "name": "okx_indicator_batch"
  }
}

Input Schema

Name	Required	Description
`bar`	No	K线粒度，默认1H
`instId`	Yes	产品ID，如 BTC-USDT
`indicators`	Yes	指标名列表，逗号分隔。可选: sma,ema,rsi,macd,bb,atr,stoch,wr,cci,obv,vwap,adx,mfi,cmf,supertrend,keltner,pattern

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Jul 30, 2026

TDQS

C2.2/5.0

Behavior2/5

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

The [L:READ] tag indicates read-only behavior, which is good, but no annotations exist to supplement. The description does not disclose other behavioral traits such as side effects, authentication needs, rate limits, or response format. For a batch tool, this is insufficient.

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?

The description is extremely concise (one line with tags and a note), but the lack of clear purpose and context makes it feel underspecified rather than efficient. It is front-loaded with tags but sacrifices clarity for brevity.

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 has 3 parameters, no output schema, and no annotations, the description is highly incomplete. It does not explain return values, limitations on batch size, or how the indicators are computed. The note to call agent_catalog outsources essential context, making the definition inadequate standalone.

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 input schema has 100% coverage with descriptions for all parameters (instId, indicators, bar). The description adds no extra meaning beyond the schema. With high schema coverage, a baseline of 3 is appropriate; the description does not degrade or enhance parameter understanding.

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 uses tags [L:READ] and CAT:[行情] but does not state a clear verb+resource. It relies on the name 'okx_indicator_batch' to imply batch indicator queries, but the text only directs users to call agent_catalog first, leaving the primary action ambiguous.

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 provides a prerequisite instruction ('请先调用 agent_catalog') but offers no guidance on when to use this tool versus alternatives like okx_indicator (singular) or okx_get_candles. There is no comparison or when-not-to-use info.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server