Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_max_size

Calculate the maximum order size for a given instrument and margin mode on OKX.

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

Input Schema

NameRequiredDescriptionDefault
ccyNo币种（仅MARGIN全仓时需要），如 USDT
instIdYes产品ID，如 BTC-USDT-SWAP。必填
tdModeYes保证金模式。cross=全仓, isolated=逐仓, cash=非保证金

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

D1.8/5.0
Behavior2/5

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

The tag '[L:READ]' hints that the tool is a read operation, but the description does not disclose other behaviors (e.g., authentication needs, rate limits, or side effects). No annotations are provided to compensate.

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 short (one line) but it is a tag, not a clear explanation. It is underspecified rather than concise, and the important information is missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description completely fails to explain what the tool returns, when to use it, or how it fits among siblings. For a tool with no output schema and minimal annotations, the description is wholly inadequate.

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 has 100% coverage with descriptions for all three parameters. The description adds no additional meaning beyond the schema, but the schema itself is adequate.

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

Purpose1/5

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

The description is a tag ('[L:READ] CAT:[账户] | → 请先调用 agent_catalog') that does not state the tool's purpose. It does not explain that the tool retrieves the maximum order size or what it does.

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 only usage guidance is '请先调用 agent_catalog' (call agent_catalog first), which implies a prerequisite but does not explain when to use this tool vs alternatives or provide exclusions.

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