Binance MCP Server

相对强弱指标

indicator_rsi

Read-only

Calculates the Relative Strength Index (RSI) from Binance futures K-line data using Wilder's smoothing, returning a stable 0-100 oscillator series to identify overbought and oversold conditions.

Instructions

直连版：拉取 K 线后计算 RSI，返回稳定序列（0-100，Wilder 平滑，period 为周期）。

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": {
      "symbol": "<symbol>",
      "interval": "<interval>"
    },
    "name": "indicator_rsi"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`period`	No
`symbol`	Yes
`interval`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv3.0.1Aug 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / interval / description
```
Removed value: -"计算周期"
```

addedInput schema / properties / interval / enum

Added value: +[
+  "1m",
+  "3m",
+  "5m",
+  "15m",
+  "30m",
+  "1h",
+  "2h",
+  "4h",
+  "6h",
+  "8h",
+  "12h",
+  "1d",
+  "3d",
+  "1w",
+  "1M"
+]

removedInput schema / properties / interval / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / interval / minimum
```
Removed value: -2
```

changedInput schema / properties / interval / type

Previous value: -"integer"New value: +"string"

addedInput schema / properties / limit

Added value: +{
+  "default": 200,
+  "maximum": 1500,
+  "minimum": 2,
+  "type": "integer"
+}

addedInput schema / properties / period

Added value: +{
+  "default": 14,
+  "maximum": 250,
+  "minimum": 2,
+  "type": "integer"
+}

addedInput schema / properties / symbol
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / values

Removed value: -{
-  "description": "价格序列（收盘价）",
-  "items": {
-    "type": "number"
-  },
-  "minItems": 1,
-  "type": "array"
-}

changedInput schema / required

Previous value: -[
-  "values",
-  "interval"
-]New value: +[
+  "symbol",
+  "interval"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv2.0.3Jun 3, 2026
- addedInput schema / properties / interval / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / interval / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / properties / values / description
```
Previous value: -"价格数组"New value: +"价格序列（收盘价）"
```
First observedv2.0.2May 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

注解已声明只读和公开数据访问，描述在此基础上补充了关键运行行为：基于K线计算、使用 Wilder 平滑、输出被限定在 0-100 的稳定序列。没有与注解矛盾，也不需要再说明副作用。

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

Conciseness5/5

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

一句话涵盖数据来源、计算方式、输出范围和关键参数，没有冗余。关键信息前置，便于快速定位；对于简单的指标工具，这种长度是合适的。

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

该工具是相对简单的指标计算工具，且已有输出 schema 和只读注解，描述提供了足够的核心语义，如周期、平滑算法和数值范围。虽缺少参数选型说明和与替代工具的边界，但对调用本身已比较完整。

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?

输入 schema 的字段描述覆盖率为 0%，描述也未对 symbol、interval、limit 给出额外语义，只提到“period 为周期”，这基本是参数名本身的同义重复。因此参数意义更多依赖字段命名和交易常识，工具描述补偿不足。

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

描述直接说明“拉取 K 线后计算 RSI”，给出具体动作、资源与输出特点（0-100、Wilder 平滑），明确区分于其他指标类工具。标题只是指标名称，但描述补充了计算方式和返回序列，使目的非常清晰。

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?

描述没有说明何时应使用本工具，也没有在 RSI 与 MACD/RSI、背离、多指标等其他关联指标之间给出选型指引。“直连版”暗示了一种实现差异，但未解释与替代方案的区别或适用场景。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server