Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_index_components

Retrieve the constituent assets of a specified index on OKX exchange, providing clear component data for analysis and trading decisions.

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": {
      "index": "<index>"
    },
    "name": "okx_get_index_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes指数名称，如 BTC-USD。必填

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.3/5.0
Behavior2/5

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

The description includes a read hint '[L:READ]' but no other behavioral traits. Without annotations, the description should disclose side effects or return format, which it does not.

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 very short but cryptic, making it hard to parse. It is concise but not effectively structured for agent understanding.

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?

The description lacks essential context about what the tool returns and how to interpret the output. With no output schema, the description should compensate but does not.

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 the parameter 'index' is described in the schema. The description adds no additional semantic value beyond the schema, so baseline score 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 does not explicitly state the tool's purpose; it only provides cryptic tags and a prerequisite hint. The name suggests it retrieves index components, but the description lacks clarity.

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_get_index_tickers. Only a prerequisite instruction to call agent_catalog first 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