indicator_macdCalculates MACD from Binance futures K-lines, returning MACD, signal, and histogram values for any symbol and interval. Specify symbol and interval to get technical indicator data.
直连版：拉取 K 线后计算 MACD，返回稳定三元组序列（macd / signal / histogram）。
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| symbol | Yes | ||
| interval | Yes | ||
| longPeriod | No | ||
| shortPeriod | No | ||
| signalPeriod | No |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v3.0.1Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / fastRemoved value: -{
- "default": 12,
- "description": "快线周期",
- "maximum": 9007199254740991,
- "minimum": 2,
- "type": "integer"
-}Input schema / properties / indicatorTypeRemoved value: -{
- "default": "EMA",
- "description": "平滑类型",
- "enum": [
- "EMA",
- "DEMA"
- ],
- "type": "string"
-}Input schema / properties / intervalAdded value: +{
+ "enum": [
+ "1m",
+ "3m",
+ "5m",
+ "15m",
+ "30m",
+ "1h",
+ "2h",
+ "4h",
+ "6h",
+ "8h",
+ "12h",
+ "1d",
+ "3d",
+ "1w",
+ "1M"
+ ],
+ "type": "string"
+}Input schema / properties / limitAdded value: +{
+ "default": 200,
+ "maximum": 1500,
+ "minimum": 2,
+ "type": "integer"
+}Input schema / properties / longPeriodAdded value: +{
+ "default": 26,
+ "maximum": 250,
+ "minimum": 2,
+ "type": "integer"
+}Input schema / properties / shortPeriodAdded value: +{
+ "default": 12,
+ "maximum": 250,
+ "minimum": 2,
+ "type": "integer"
+}Input schema / properties / signalRemoved value: -{
- "default": 9,
- "description": "信号线周期",
- "maximum": 9007199254740991,
- "minimum": 2,
- "type": "integer"
-}Input schema / properties / signalPeriodAdded value: +{
+ "default": 9,
+ "maximum": 100,
+ "minimum": 2,
+ "type": "integer"
+}Input schema / properties / slowRemoved value: -{
- "default": 26,
- "description": "慢线周期",
- "maximum": 9007199254740991,
- "minimum": 2,
- "type": "integer"
-}Input schema / properties / symbolAdded value: +{
+ "type": "string"
+}Input schema / properties / valuesRemoved value: -{
- "description": "价格序列（收盘价）",
- "items": {
- "type": "number"
- },
- "minItems": 1,
- "type": "array"
-}Input schema / requiredPrevious value: -[
- "values"
-]New value: +[
+ "symbol",
+ "interval"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "histogram": {
+ "type": "number"
+ },
+ "macd": {
+ "type": "number"
+ },
+ "signal": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "macd",
+ "signal",
+ "histogram"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "data"
+ ],
+ "type": "object"
+}v2.0.3Input schema / properties / fast / descriptionPrevious value: -"快线"New value: +"快线周期"Input schema / properties / fast / maximumAdded value: +9007199254740991Input schema / properties / fast / minimumAdded value: +2Input schema / properties / fast / typePrevious value: -"number"New value: +"integer"Input schema / properties / indicatorType / defaultAdded value: +"EMA"Input schema / properties / indicatorType / enumPrevious value: -[
- "EMA",
- "RMA",
- "SMA",
- "WMA",
- "WSMA"
-]New value: +[
+ "EMA",
+ "DEMA"
+]Input schema / properties / signal / descriptionPrevious value: -"信号线"New value: +"信号线周期"Input schema / properties / signal / maximumAdded value: +9007199254740991Input schema / properties / signal / minimumAdded value: +2Input schema / properties / signal / typePrevious value: -"number"New value: +"integer"Input schema / properties / slow / descriptionPrevious value: -"慢线"New value: +"慢线周期"Input schema / properties / slow / maximumAdded value: +9007199254740991Input schema / properties / slow / minimumAdded value: +2Input schema / properties / slow / typePrevious value: -"number"New value: +"integer"Input schema / properties / values / descriptionPrevious value: -"价格数组"New value: +"价格序列（收盘价）"v2.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds some behavioral context beyond the annotations by revealing that the tool pulls K-lines, computes MACD, and returns a stable sequence of triples. The annotations already cover read-only and open-world hints, so the burden is lower. However, it does not mention edge cases, error conditions, or how the return sequence is structured relative to time or limit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence that front-loads the core behavior (K-line fetch, MACD calculation, output shape). Every phrase earns its place, though the '直连版本' wording is fuzzy and consumes space without being fully informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given schema coverage of 0%, six parameters, and a sibling ecosystem full of choosing ambiguity, this description is far from complete. It provides an output shape, so the output schema can carry some burden, but it totally fails to explain parameter semantics or give usage context, making the tool under-specified for an correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not mention or explain any of the 6 parameters. Even the key MACD parameters like longPeriod, shortPeriod, and signalPeriod are omitted entirely, so the agent receives no semantic explanation for the parameters beyond raw schema defaults.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('拉取 K 线后计算 MACD') and identifies the output as a stable triple sequence (macd / signal / histogram). '直连版' hints at a distinguishing mode and distinguishes this from combined indicator siblings like indicator_macd_rsi, though the meaning of '直连版' is not fully explained.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 instead of the many sibling indicators (e.g., indicator_macd_rsi, indicator_multi, indicator_rsi). The phrase '直连版' implies some mode difference, but it never states when an agent should choose this tool or when it should not. There is no explicit exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/iuk-ink/binance-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server