TraderSpy

This connector has been deprecated

Duplicate entry for the same endpoint. TraderSpy is actively maintained; this particular listing is simply not the one we keep current. Use TraderSpy instead: it is published from the official MCP registry, so its description and tool list refresh automatically with every release.

get_technical_indicators

Read-onlyIdempotent

Technical analysis for a crypto futures symbol. 19 indicators: RSI, MACD, EMA, SMA, Bollinger Bands, ATR, ADX (+DI/−DI), Stochastic, OBV (with price divergence), VWAP, CCI, MFI, Williams %R, ROC, SuperTrend, Ichimoku, Keltner Channels, classic pivot points and swing support/resistance levels. Every indicator returns its current value, the previous bar, a rising/falling/flat direction, a short series history and — where it applies — zones and crossovers. EMA/SMA accept several periods at once (default 20/50/200); every period is overridable via periods. Pass intervals (up to 3) to get 1h/4h/1d in ONE call with a multi-timeframe confluence verdict. Each timeframe also carries a summary (bias, trend, momentum, volatility, volume, plain-language notes) computed from a fixed indicator set — quote its notes rather than the raw score. For several coins pass symbols (up to 3) instead of one call per coin: ONE call and one quota unit, one entry per symbol in data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	No	Trading pair symbol, e.g. BTCUSDT. For several pairs pass `symbols` instead.
`history`	No	Prior values returned per indicator as `series` (oldest → newest, length history + 1). 0 = latest only.
`periods`	No	Optional period overrides, e.g. {"ema":[9,21,55,200],"rsi":7}
`symbols`	No	Up to 3 trading pairs in ONE call (one quota unit), e.g. ["BTCUSDT","ETHUSDT","SOLUSDT"]. The response then carries one entry per symbol in `data`, each shaped like the single-symbol response.
`interval`	No	Candle timeframe. Ignored when `intervals` is given.	1h
`intervals`	No	Up to 3 timeframes in ONE call (one quota unit), e.g. ["1h","4h","1d"]. The response then carries per-timeframe results plus a `confluence` verdict.
`indicators`	No	Indicators to compute. `levels` = swing support/resistance from price structure, `pivots` = classic floor pivots from the previous day.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Present when `symbols` was passed, and then the only place the results are: one entry per symbol, in the requested order, each exactly the single-symbol response above ({ symbol, interval, price, candles, indicators + summary or timeframes + confluence, settings, warnings }) — or { symbol, error: "no_data", message } when no candles are stored for it.
`count`	No	Entries in `data`
`price`	No	Latest close on the primary timeframe, or null when no candles are stored
`symbol`	No
`candles`	No	Closed candles the primary timeframe was computed on
`summary`	No	Single-timeframe call only: bias, score, trend, momentum, volatility, volume, notes[]. Omitted when `timeframes` is present.
`interval`	No	Primary timeframe (the first requested one)
`settings`	No	Echo of what was computed: indicators, history, resolved periods
`warnings`	No
`confluence`	No	Multi-timeframe agreement: { aligned, bias, byInterval }
`indicators`	No	Single-timeframe call only: requested indicators keyed by name. Each carries value, previous, direction, series and indicator-specific fields (zone, crossover, stack, levels…); { value: null, reason: "insufficient_data" } when the tape is too short. Omitted when `timeframes` is present — read them there.
`timeframes`	No	Present when several intervals were requested: one { interval, price, candles, indicators, summary } per timeframe, in the requested order. The top-level indicators/summary are omitted in that case.
`lastCandleOpenTime`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 3, 2026

changedInput schema / properties / symbol / description

Previous value: -"Trading pair symbol, e.g. BTCUSDT"New value: +"Trading pair symbol, e.g. BTCUSDT. For several pairs pass `symbols` instead."

addedInput schema / properties / symbols

Added value: +{
+  "description": "Up to 3 trading pairs in ONE call (one quota unit), e.g. [\"BTCUSDT\",\"ETHUSDT\",\"SOLUSDT\"]. The response then carries one entry per symbol in `data`, each shaped like the single-symbol response.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 3,
+  "minItems": 1,
+  "type": "array"
+}

removedInput schema / required
```
Removed value: -[
-  "symbol"
-]
```

addedOutput schema / properties / count

Added value: +{
+  "description": "Entries in `data`",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / data

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Present when `symbols` was passed, and then the only place the results are: one entry per symbol, in the requested order, each exactly the single-symbol response above ({ symbol, interval, price, candles, indicators + summary or timeframes + confluence, settings, warnings }) — or { symbol, error: \"no_data\", message } when no candles are stored for it."
+}

Changed3 schema fields changedSep 9, 2026

changedOutput schema / properties / indicators / description

Previous value: -"Requested indicators keyed by name (primary timeframe). Each carries value, previous, direction, series and indicator-specific fields (zone, crossover, stack, levels…); { value: null, reason: \"insufficient_data\" } when the tape is too short."New value: +"Single-timeframe call only: requested indicators keyed by name. Each carries value, previous, direction, series and indicator-specific fields (zone, crossover, stack, levels…); { value: null, reason: \"insufficient_data\" } when the tape is too short. Omitted when `timeframes` is present — read them there."

changedOutput schema / properties / summary / description

Previous value: -"Interpretation layer: bias, score, trend, momentum, volatility, volume, notes[]"New value: +"Single-timeframe call only: bias, score, trend, momentum, volatility, volume, notes[]. Omitted when `timeframes` is present."

changedOutput schema / properties / timeframes / description

Previous value: -"Present when several intervals were requested: one { interval, price, indicators, summary } per timeframe"New value: +"Present when several intervals were requested: one { interval, price, candles, indicators, summary } per timeframe, in the requested order. The top-level indicators/summary are omitted in that case."

Changed17 schema fields changedSep 8, 2026

addedInput schema / properties / history

Added value: +{
+  "default": 5,
+  "description": "Prior values returned per indicator as `series` (oldest → newest, length history + 1). 0 = latest only.",
+  "maximum": 20,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / indicators / description

Previous value: -"Technical indicators to compute"New value: +"Indicators to compute. `levels` = swing support/resistance from price structure, `pivots` = classic floor pivots from the previous day."

changedInput schema / properties / indicators / items / enum

Previous value: -[
-  "rsi",
-  "macd",
-  "ema",
-  "sma",
-  "bollinger",
-  "atr",
-  "adx",
-  "stochastic",
-  "obv",
-  "vwap",
-  "cci",
-  "mfi",
-  "williamsR"
-]New value: +[
+  "rsi",
+  "macd",
+  "ema",
+  "sma",
+  "bollinger",
+  "atr",
+  "adx",
+  "stochastic",
+  "obv",
+  "vwap",
+  "cci",
+  "mfi",
+  "williamsR",
+  "roc",
+  "supertrend",
+  "ichimoku",
+  "keltner",
+  "pivots",
+  "levels"
+]

changedInput schema / properties / indicators / maxItems
```
Previous value: -13New value: +19
```

changedInput schema / properties / interval / description

Previous value: -"Candle interval/timeframe"New value: +"Candle timeframe. Ignored when `intervals` is given."

addedInput schema / properties / intervals

Added value: +{
+  "description": "Up to 3 timeframes in ONE call (one quota unit), e.g. [\"1h\",\"4h\",\"1d\"]. The response then carries per-timeframe results plus a `confluence` verdict.",
+  "items": {
+    "enum": [
+      "1m",
+      "5m",
+      "15m",
+      "1h",
+      "4h",
+      "1d"
+    ],
+    "type": "string"
+  },
+  "maxItems": 3,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / periods

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional period overrides, e.g. {\"ema\":[9,21,55,200],\"rsi\":7}",
+  "properties": {
+    "adx": {
+      "description": "ADX period (default 14)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "atr": {
+      "description": "ATR period (default 14)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "bollinger": {
+      "description": "Bollinger period (default 20)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "bollingerStdDev": {
+      "description": "Bollinger std-dev multiplier (default 2)",
+      "maximum": 5,
+      "minimum": 0.5,
+      "type": "number"
+    },
+    "cci": {
+      "description": "CCI period (default 20)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "ema": {
+      "description": "EMA periods, up to 4 (default [20, 50, 200])",
+      "items": {
+        "maximum": 500,
+        "minimum": 2,
+        "type": "integer"
+      },
+      "maxItems": 4,
+      "minItems": 1,
+      "type": "array"
+    },
+    "keltner": {
+      "description": "Keltner EMA period (default 20)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "keltnerAtr": {
+      "description": "Keltner ATR period (default 10)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "keltnerMultiplier": {
+      "description": "Keltner ATR multiplier (default 2)",
+      "maximum": 10,
+      "minimum": 0.5,
+      "type": "number"
+    },
+    "macdFast": {
+      "description": "MACD fast EMA (default 12)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "macdSignal": {
+      "description": "MACD signal EMA (default 9)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "macdSlow": {
+      "description": "MACD slow EMA (default 26)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "mfi": {
+      "description": "MFI period (default 14)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "obv": {
+      "description": "OBV averaging window (default 20)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "roc": {
+      "description": "Rate-of-change period (default 12)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "rsi": {
+      "description": "RSI period (default 14)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "sma": {
+      "description": "SMA periods, up to 4 (default [20, 50, 200])",
+      "items": {
+        "maximum": 500,
+        "minimum": 2,
+        "type": "integer"
+      },
+      "maxItems": 4,
+      "minItems": 1,
+      "type": "array"
+    },
+    "stochastic": {
+      "description": "Stochastic %K period (default 14)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "stochasticSignal": {
+      "description": "Stochastic %D smoothing (default 3)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "supertrend": {
+      "description": "SuperTrend ATR period (default 10)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "supertrendMultiplier": {
+      "description": "SuperTrend ATR multiplier (default 3)",
+      "maximum": 10,
+      "minimum": 0.5,
+      "type": "number"
+    },
+    "vwap": {
+      "description": "Rolling VWAP window in bars (default 48)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "williamsR": {
+      "description": "Williams %R period (default 14)",
+      "maximum": 500,
+      "minimum": 2,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / candles

Added value: +{
+  "description": "Closed candles the primary timeframe was computed on",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / confluence

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Multi-timeframe agreement: { aligned, bias, byInterval }"
+}

changedOutput schema / properties / indicators / description

Previous value: -"Requested indicators keyed by name; shape differs per indicator"New value: +"Requested indicators keyed by name (primary timeframe). Each carries value, previous, direction, series and indicator-specific fields (zone, crossover, stack, levels…); { value: null, reason: \"insufficient_data\" } when the tape is too short."

addedOutput schema / properties / interval / description

Added value: +"Primary timeframe (the first requested one)"

addedOutput schema / properties / lastCandleOpenTime

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "format": "date-time",
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / price / description

Previous value: -"Latest close, or null when no candles are stored"New value: +"Latest close on the primary timeframe, or null when no candles are stored"

addedOutput schema / properties / settings

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Echo of what was computed: indicators, history, resolved periods"
+}

addedOutput schema / properties / summary

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Interpretation layer: bias, score, trend, momentum, volatility, volume, notes[]"
+}

addedOutput schema / properties / timeframes

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Present when several intervals were requested: one { interval, price, indicators, summary } per timeframe"
+}

addedOutput schema / properties / warnings

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedAug 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description focuses on output behavior: each indicator returns current value, prior bar, direction, a `series` history, and where applicable zones/crossovers. It also discloses the quota model ('ONE call and one quota unit'), which is genuinely useful context beyond the annotations.

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?

Front-loaded with the core purpose, then indicator list, then batching behavior. Dense but every sentence carries information; the long indicator enumeration is justified given it defines the tool's scope. Slightly heavy but not padded.

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

Completeness5/5

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

For a complex, multi-mode tool this is complete: batching semantics, quota implications, per-timeframe confluence, and the summary/notes guidance are all covered. An output schema exists and return shapes are described, so nothing an agent needs to invoke it correctly is missing.

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 every parameter (including the 20 nested period overrides) is already documented. The description reinforces the high-value ones (EMA/SMA multi-period, `periods` override, batching) but adds no syntax or defaults the schema lacks — baseline 3 is appropriate.

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?

States a specific verb+resource ('Technical analysis for a crypto futures symbol') and enumerates exactly what is computed — 19 named indicators plus pivots/levels. An agent can immediately tell this apart from siblings like get_candles or get_price, which return raw data rather than derived signals.

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?

Gives explicit operational guidance: pass `symbols` (up to 3) instead of one call per coin, pass `intervals` to get 1h/4h/1d in one call, and 'quote its notes rather than the raw score'. This shapes correct usage well, though it never names a sibling alternative or states when NOT to use the tool.

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

All TraderSpy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?