Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_predictions_split

Split OKX predictions into a specified number of parts for granular analysis. Input the quantity of splits to divide prediction results.

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": {
      "amount": "<amount>"
    },
    "name": "okx_predictions_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes拆分数量（必填）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only discloses that it is a write operation via '[L:WRITE]', but does not describe side effects, required permissions, or whether the split is reversible.

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

Conciseness3/5

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

The description is very short, but it is not well-structured. It uses brackets and a symbol inconsistently. Still, it is concise and avoids unnecessary words.

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 is a write operation with no output schema, the description should explain what splitting does and what happens after. It only mentions a prerequisite, leaving the agent without a clear understanding of the tool's effect.

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 only parameter 'amount' has schema description '拆分数量（必填）' meaning 'split quantity (required)'. The tool description does not add further meaning, but schema coverage is 100%, 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 '[L:WRITE] CAT:[预测] | → 请先调用 agent_catalog' is vague. It indicates a write operation and a category but does not clearly state that this tool splits predictions. The verb 'split' is only in the name, not explained.

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 advises to call agent_catalog first, which is a prerequisite. However, it offers no guidance on when to use this tool vs alternatives like okx_predictions_merge or other okx_predictions tools.

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