Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agent_copy_trader_search

Filter and rank top copy traders by PnL, win rate, or copy count. Includes copy trading guidance for SPOT and SWAP.

Instructions

[L:READ] CAT:[跟单] | 按收益率/胜率/回撤筛选最优带单员，附跟单指引

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agent_copy_trader_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNNo
sortByNopnl
instTypeNoSWAP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.7/5.0
Behavior2/5

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

The description includes a '[L:READ]' tag hinting at read-only behavior, but since no annotations are provided, this carries the burden. It does not disclose other traits like required permissions, rate limits, or state changes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and uses tags for categorization. It is front-loaded with key information, but the formatting (brackets and colons) is somewhat noisy.

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?

Given the tool has 3 parameters, no output schema, and no parameter descriptions, the description fails to explain return format, pagination, or the meaning of 'optimal.' It is insufficient for an agent to use without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions three performance metrics (return rate, win rate, drawdown), but only two align with sortBy options (pnl, winRate). The topN and instType parameters are unaddressed, leading to partial coverage.

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

Purpose4/5

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

The description clearly states it filters best lead traders by return rate, win rate, and drawdown, with a copy trading guide. The verb 'filter' and resource 'lead traders' are specific. However, it lacks differentiation from sibling copy trading tools, and the Chinese text may reduce clarity for non-Chinese agents.

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 like okx_get_public_lead_traders. It does not provide context for selection or exclusion.

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