Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_system_status

Check the current operational status of the OKX exchange to confirm platform availability and detect ongoing maintenance.

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_get_system_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 provided, the description carries the full burden of disclosing behavioral traits. It only indicates read-only via '[L:READ]', but does not detail what data is returned, if side effects exist, or any other behavioral aspects. This is minimally informative.

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 includes a tag, category, and instruction. While concise, it sacrifices clarity for brevity. The structure is organized but the content is insufficient.

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 simplicity (no parameters, no output schema), the description should still explain what the tool returns or what 'system status' means. It fails to provide a complete understanding, leaving the agent uncertain about the output's nature.

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 has zero parameters, so schema description coverage is trivially 100%. The description adds no extra parameter meaning, which is acceptable given the absence of parameters.

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 cryptic tags ('[L:READ]', 'CAT:[行情]') and an instruction to call agent_catalog, but does not explicitly state that the tool retrieves the OKX system status. The purpose is vaguely implied by the tool name, but the description adds no concrete clarity.

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 includes a prerequisite ('→ 请先调用 agent_catalog'), providing some usage context. However, it lacks guidance on when to use this tool versus alternative tools like okx_get_system_time or okx_get_account_rate_limit, and does not describe appropriate scenarios.

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