Skip to main content
Glama
Binance MCP Server

Binance MCP Server

平均真实波幅

indicator_atr
Read-only

Calculate Average True Range (ATR) from Binance K-line data to measure volatility, using Wilder smoothing for stable indicator values.

Instructions

直连版:拉取 K 线后计算 ATR,返回稳定序列(衡量波动,默认 Wilder 平滑)。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
periodNo
symbolYes
intervalYes

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv3.0.1
    • 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 / candles
      Removed value: -{
      -  "description": "HLC K 线数组 [{high, low, close}]",
      -  "items": {
      -    "properties": {
      -      "close": {
      -        "type": "number"
      -      },
      -      "high": {
      -        "type": "number"
      -      },
      -      "low": {
      -        "type": "number"
      -      }
      -    },
      -    "required": [
      -      "high",
      -      "low",
      -      "close"
      -    ],
      -    "type": "object"
      -  },
      -  "minItems": 1,
      -  "type": "array"
      -}
    • addedInput schema / properties / interval
      Added value: +{
      +  "enum": [
      +    "1m",
      +    "3m",
      +    "5m",
      +    "15m",
      +    "30m",
      +    "1h",
      +    "2h",
      +    "4h",
      +    "6h",
      +    "8h",
      +    "12h",
      +    "1d",
      +    "3d",
      +    "1w",
      +    "1M"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 200,
      +  "maximum": 1500,
      +  "minimum": 2,
      +  "type": "integer"
      +}
    • removedInput schema / properties / period / description
      Removed value: -"计算周期"
    • changedInput schema / properties / period / maximum
      Previous value: -9007199254740991New value: +100
    • removedInput schema / properties / smoothingType
      Removed value: -{
      -  "default": "EMA",
      -  "enum": [
      -    "EMA",
      -    "RMA",
      -    "SMA",
      -    "WMA",
      -    "WSMA"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / symbol
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "candles"
      -]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"
      +}
  2. Changed6 schema fields changedv2.0.3
    • changedInput schema / properties / candles / description
      Previous value: -"HLC 数组"New value: +"HLC K 线数组 [{high, low, close}]"
    • removedInput schema / properties / interval
      Removed value: -{
      -  "description": "计算周期",
      -  "minimum": 2,
      -  "type": "number"
      -}
    • addedInput schema / properties / period
      Added value: +{
      +  "default": 14,
      +  "description": "计算周期",
      +  "maximum": 9007199254740991,
      +  "minimum": 2,
      +  "type": "integer"
      +}
    • addedInput schema / properties / smoothingType / default
      Added value: +"EMA"
    • removedInput schema / properties / smoothingType / description
      Removed value: -"平滑类型"
    • changedInput schema / required
      Previous value: -[
      -  "candles",
      -  "interval"
      -]New value: +[
      +  "candles"
      +]
  3. First observedv2.0.2

TDQS

A4/5.0
Behavior4/5

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

除注解readOnlyHint已经说明只读外,描述额外说明了计算过程(拉取K线、计算ATR)、默认平滑方式(Wilder)和返回特性(稳定序列),这补充了注解之外的实际执行行为。没有与注解矛盾。

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.

Completeness3/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?

当前参数有4个,schema描述覆盖率为0%,描述中几乎没有对参数进行额外解释。只通过“默认Wilder平滑”间接暗示了period的默认风格,但symbol、interval、limit等参数均未在描述中说明对应语义或使用建议,描述未帮助填充schema空白。

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线后计算ATR,并指出其为波动率工具,同时提到默认Wilder平滑。与其他指标工具(SMA/EMA/MACD等)在功能上有明显区分,动词和资源明确。

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

描述中通过“衡量波动”点明了使用场景,且在指标类工具中能自然引导Agent在需要波动率时选择该工具。但未明说何时不应使用或与其他波动率工具的取舍,缺少明确的排除性指引。

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