Skip to main content
Glama
Sign In
AkTools MCP Server

AkTools MCP Server

by fastmcp-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

获取加密货币杠杆多空比

okx_loan_ratios

Retrieve OKX crypto loan ratios, cumulative borrowed quote vs base currency amounts, for BTC or ETH over 5m/1H/1D intervals. Gauge market sentiment with this data.

Instructions

获取OKX加密货币借入计价货币与借入交易货币的累计数额比值

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

Input Schema

NameRequiredDescriptionDefault
periodNo时间粒度，仅支持: [5m/1H/1D] 注意大小写，仅分钟为小写m1h
symbolNo币种，格式: BTC 或 ETHBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.14

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It only states the computation goal but lacks any behavioral context such as whether the operation is read-only, data freshness, potential rate limits, or return format. This is a significant gap for a data retrieval tool.

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 a single concise sentence with no wasted words. It is front-loaded with the action and resource, though it could be slightly clearer given the title mismatch.

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?

The tool has no annotations, no output schema, and a minimal description. It explains the metric computed but does not elaborate on how the ratio is interpreted, possible time ranges, or return structure. Given the availability of sibling tools and the need to select correctly, more context would be valuable.

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 description coverage is 100%, so parameters are already well-documented. The description does not add extra meaning beyond the schema, so a baseline of 3 is appropriate.

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 the action (获取/get) and the resource (OKX cryptocurrency cumulative ratio of borrowed quote to trading currency), distinguishing it from sibling tools like okx_prices and okx_taker_volume. However, the title uses '杠杆多空比' (leverage long/short ratio) which slightly differs from the description's wording, creating minor ambiguity.

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 is provided on when to use this tool versus alternatives. The description does not mention use cases, scenarios, or exclusions, leaving the agent to infer applicability.

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