Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_estimated_price

Retrieve the estimated price for a specific options contract (instId) from OKX exchange. Use this tool to get pricing estimates for options trading.

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>"
    },
    "name": "okx_get_estimated_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
instIdYes期权产品ID，如 BTC-USD-260612-64000-C。必填

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, and the description only indicates a read operation and public category. It does not disclose authentication needs, rate limits, return values, or other behavioral traits beyond the minimal read hint.

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 short but cryptic, using abbreviations and a prerequisite instruction that does not explain the tool itself. It is not front-loaded with a clear purpose statement, and the structure is confusing.

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 no output schema and low complexity, the description should explain what the tool returns and when it is useful. It lacks any explanation of the output or the context in which to use the estimated price, relying on a reference to agent_catalog.

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 fully describes the single parameter `instId` with a clear example and requirement. The description adds no additional meaning, but schema coverage is 100%, 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 provides a read label and category but does not explicitly state what the tool does. The tool name suggests it retrieves an estimated price, likely for options, but the description is cryptic and fails to clarify the purpose.

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. The description includes a prerequisite to call agent_catalog, but does not help the agent decide when to invoke this tool over sibling tools like okx_get_ticker or okx_get_instruments.

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