Skip to main content
Glama
Sign In
hvip MCP Server

hvip MCP Server

by okx-wallet-H
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

okx_get_account_greeks

Retrieve the Greeks (delta, gamma, etc.) for options positions on OKX. Specify underlying, instrument type, or product family to get account risk metrics.

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

Input Schema

NameRequiredDescriptionDefault
ulyNo标的指数，如 BTC-USD
instIdNo产品ID
instTypeNo产品类型。SPOT/MARGIN/SWAP/FUTURES/OPTION
instFamilyNo产品族，如 BTC-USD

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 must carry behavioral disclosure. '[L:READ]' signals read-only, but no further behavioral traits (e.g., mutability, authorization needs, rate limits) are mentioned. The dependency on agent_catalog is noted but incompletely.

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 (one line with tag and instruction), but its brevity sacrifices clarity. It could be improved by adding a brief purpose statement. Front-loading a READ tag is helpful but 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 that this tool likely returns complex options greeks data and has no output schema, the description should provide more context about what the tool returns or how it filters. The current description is too minimal to guide correct usage.

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?

Schema coverage is 100%, so the description does not need to re-iterate parameter details. However, it adds no additional context or examples for the parameters (uly, instId, instType, instFamily). Baseline score of 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 says '[L:READ] CAT:[账户]' but does not explicitly state that the tool retrieves options greeks. The purpose is implied by the tool name but not clarified. The instruction '请先调用 agent_catalog' (call agent_catalog first) suggests a prerequisite but not the core function.

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 indicates a prerequisite ('call agent_catalog first') but provides no guidance on when to use this tool versus alternatives. The sibling list contains many account-related tools, but no differentiation is offered.

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