hvip MCP Server

okx_adjust_collateral

Add or reduce collateral for a position on OKX by specifying currency, amount, and direction.

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>",
      "amt": "<amt>",
      "side": "<side>"
    },
    "name": "okx_adjust_collateral"
  }
}

Input Schema

Name	Required	Description
`amt`	Yes	调整数量。必填
`ccy`	Yes	抵押币种。必填
`side`	Yes	方向。add=增加抵押, reduce=减少抵押

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Jul 30, 2026

TDQS

D1.6/5.0

Behavior1/5

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

With no annotations, the description should disclose behavioral traits. It only mentions a prerequisite (calling agent_catalog) but does not describe side effects, authorization needs, or other behaviors.

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 but fails to provide essential information. It is under-speficiation rather than conciseness. The structure is a single line with tags and an instruction.

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?

For a tool that modifies collateral, the description is completely inadequate. It lacks any explanation of the tool's operation, return values, or context. Schema covers params but no output schema exists.

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 each parameter has a description. The description adds no additional meaning beyond the schema, so baseline 3 applies.

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 does not state what the tool does; it only contains a tag and an instruction to call another tool. The purpose is missing.

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 instruction '请先调用 agent_catalog' hints at a prerequisite but does not clarify usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server