Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_event_instruments

Retrieves event instruments by series ID on OKX exchange. Call agent_catalog first to obtain available series IDs.

Instructions

[L:READ] CAT:[预测] | → 请先调用 agent_catalog

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": "okx_event_instruments"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdNo事件系列ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

D1.9/5.0
Behavior2/5

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

No annotations provided. The '[L:READ]' tag hints at read-only but is not standard. No mention of side effects, permissions, rate limits, or data returned. The description does not disclose behavioral traits beyond the tag.

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?

Extremely short but not front-loaded with essential information. The few words are cryptic and barely more than a label. Conciseness is not helpful when it omits critical purpose and usage details.

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?

No output schema, no explanation of return values, and the domain (event instruments) is complex. The agent lacks essential context to understand what this tool returns or how to use results. Very incomplete.

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?

The schema describes seriesId with a Chinese description (事件系列ID). The description adds no further meaning or usage context for the parameter. With 100% schema coverage, baseline is 3, but the description fails to add value.

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 is cryptic ('[L:READ] CAT:[预测]') and only instructs to call agent_catalog first. It does not state what the tool does (e.g., 'get event instruments'). The name gives some clue but the description fails to clarify the purpose.

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 guidance is '请先调用 agent_catalog' (call agent_catalog first), implying a dependency. No explicit when-to-use or when-not-to-use compared to siblings like okx_get_event_events or outcomes_list_events.

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