Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_easy_convert

Convert one cryptocurrency to another on OKX exchange. Specify the currency to sell, currency to buy, and the amount to execute the conversion.

Instructions

[L:WRITE] 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": {
      "fromCcy": "<fromCcy>",
      "toCcy": "<toCcy>",
      "sz": "<sz>"
    },
    "name": "okx_easy_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
szYes卖出数量
toCcyYes买入币种，如 BTC
fromCcyYes卖出币种，如 USDT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only labels the tool as write operation ([L:WRITE]), but does not disclose other behavioral traits such as required permissions, side effects, rate limits, or return behavior.

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 not effectively concise. It includes obscure brackets and a directive that wastes characters. The core purpose is not front-loaded, and the brevity sacrifices clarity.

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?

Given the tool is a write operation with three required parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the tool returns, preconditions beyond calling agent_catalog, or any behavioral context.

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 covers all three parameters with descriptions in Chinese (e.g., '卖出数量', '买入币种', '卖出币种'). The description adds no extra meaning beyond what the schema already provides, so baseline 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 uses a category label and a reference to agent_catalog, but does not clearly state what the tool does. The name 'easy_convert' hints at a conversion operation, but the description lacks a specific verb and resource, making it hard to distinguish from other tools like okx_convert_trade.

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 says '→ 请先调用 agent_catalog' (please call agent_catalog first), implying a prerequisite, but provides no guidance on when to use this tool versus alternatives. No context for appropriate usage scenarios is given.

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