Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_leverage_info

Retrieve leverage information for a specified OKX instrument and margin mode (isolated or cross).

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

Input Schema

NameRequiredDescriptionDefault
instIdYes产品ID，如 BTC-USDT-SWAP
mgnModeYes保证金模式：isolated=逐仓，cross=全仓

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?

The description includes '[L:READ]' hinting at read-only behavior, but lacks details on what data is returned (e.g., current leverage, max leverage), error handling, or any side effects. With no annotations, more transparency is needed.

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 extremely brief but cryptic, sacrificing clarity for brevity. The prerequisite note is not front-loaded with the main purpose, and the format is not user-friendly for an AI agent.

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?

With no output schema, the description should at least indicate what the tool returns (e.g., leverage info). It only provides a prerequisite, leaving the return value and typical usage incomplete. Important context is missing.

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 clear descriptions for both parameters ('instId' and 'mgnMode'). The description adds no extra semantic value, so 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 'CAT:[账户]' and prerequisite note do not clearly state that this tool retrieves leverage information for an instrument and margin mode. The purpose is vague and relies on the tool name for understanding.

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 calling 'agent_catalog' first, providing a prerequisite, but offers no guidance on when to use this tool instead of alternatives like 'okx_set_leverage' or 'okx_get_positions'. No contextual differentiation.

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