Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_underlying

Retrieve underlying assets for OKX perpetual swaps, futures, or options. Specify product type to filter results.

Instructions

[L:READ] CAT:[公共] | → 请先调用 agent_catalog

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "okx_get_underlying"
  }
}

Input Schema

NameRequiredDescriptionDefault
instTypeNo产品类型。SWAP=永续, FUTURES=交割, OPTION=期权。不填返回全部

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 are provided, so the description must disclose behavior. It includes a read hint '[L:READ]' and a category 'CAT:[公共]', but lacks details on side effects, dependencies, or return characteristics. The prerequisite hint is present but not elaborated.

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 short, consisting of two fragments. It is concise but at the expense of clarity. It includes a useful prerequisite instruction, but the overall lack of structure and completeness reduces its effectiveness.

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?

Given the large number of sibling tools, no output schema, and only one parameter, the description fails to provide sufficient context. It does not explain what the tool returns, how it differs from similar OKX tools, or what the prerequisite entails. The description is incomplete for an agent to use it correctly.

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 schema already provides a clear description of the 'instType' parameter with enum values and their meanings. The tool description adds no additional semantic value beyond what the schema offers, so a baseline score of 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 vague: it only indicates the tool is read-only and requires a prior call to 'agent_catalog', but does not explain what 'underlying' means or what the tool returns. The name suggests it retrieves underlying information for OKX instruments, but the purpose is not clearly stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a prerequisite ('call agent_catalog first'), which is a useful guideline. However, it does not specify when to use this tool versus alternatives among the many sibling tools, nor does it give any exclusion conditions.

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