Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_books_full

Retrieves the complete order book of an OKX trading pair, with an optional depth parameter to limit the number of levels.

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_books_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNo深度档位，默认全量，可选限制
instIdYes产品ID，如 BTC-USDT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It only includes a read hint via '[L:READ]' (not part of description) and the prerequisite, missing details on return format, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one line), achieving conciseness, but the content is minimal. The prerequisite instruction is useful, yet the description could be clearer about the tool's function.

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 tool has 2 parameters and no output schema or annotations, the description is insufficient. It does not explain what data is returned, how to interpret results, or the significance of 'full' in the tool name.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning to parameters beyond the schema, which already documents 'instId' and 'depth'.

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 only provides a category tag 'CAT:[行情]' and a prerequisite, but does not explicitly state what the tool does. The tool name 'get_books_full' suggests retrieving full order book data, but the description lacks a clear verb-resource statement.

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 instructs to call 'agent_catalog' first, which is a prerequisite, but offers no guidance on when to use this tool versus alternatives like 'okx_get_orderbook' or other market data tools.

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