hvip MCP Server

okx_get_instruments

Retrieve trading instrument details from OKX by product type, with optional specific instrument 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": {
      "instType": "<instType>"
    },
    "name": "okx_get_instruments"
  }
}

Input Schema

Name	Required	Description	Default
`instId`	No	指定产品ID，不填则返回全量
`instType`	Yes	产品类型

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Jul 30, 2026

TDQS

D1.8/5.0

Behavior2/5

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

The description gives a read hint ([L:READ]) but no annotations exist. It fails to disclose any behavioral traits such as data scope, rate limits, or side effects.

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 but is under-specified and cryptic rather than concise. It wastes space on unclear notes.

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?

For a tool that retrieves instruments from a large exchange with many similar tools, the description lacks any detail on returned data, filtering, or prerequisites, making it nearly useless.

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% so the baseline is 3. The description adds no parameter information beyond what the schema already provides.

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

Purpose1/5

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

The description does not state what the tool does; it only provides a cryptic categorization note and a prerequisite. The purpose is implied by the name but not clarified.

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 like okx_search_instruments. The hint to call agent_catalog is vague and unexplained.

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

Deploy Server