Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_long_short_ratio

Retrieve long/short ratio for a cryptocurrency from OKX exchange. Specify coin and optional time range to analyze market sentiment.

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": {
      "ccy": "<ccy>"
    },
    "name": "okx_get_long_short_ratio"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccyYes币种，如 BTC、ETH
endNo结束时间戳（毫秒）
beginNo开始时间戳（毫秒）

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 bears full responsibility. The 'L:READ' tag suggests read-only, but no further behavior (e.g., rate limits, data range, response structure) is disclosed. This is insufficient for a data retrieval tool.

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 concise (one line) but lacks substantial content beyond tags and a prerequisite. It earns its place but sacrifices completeness for brevity.

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?

No output schema and minimal description. The tool has 3 parameters (1 required) and is in a context of many similar tools. The description does not provide enough information for an agent to confidently use it without additional inference.

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% with each parameter having a description in Chinese. The description does not add extra semantic meaning beyond the schema (e.g., examples or formatting hints). Baseline 3 is appropriate given high coverage.

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

Purpose3/5

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

The description states 'L:READ' and 'CAT:[Statistics]' but does not explicitly state that the tool retrieves the long/short ratio for a given currency. The name is clear, but the description relies on it. Sibling tools like okx_get_top_trader_long_short_ratio exist, but no differentiation is provided.

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 mentions '→ 请先调用 agent_catalog' (please call agent_catalog first), indicating a prerequisite. However, it gives no guidance on when to use this tool vs. alternatives like okx_get_contracts_long_short_ratio or okx_get_long_short_account_ratio.

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