Skip to main content
Glama

Loading technical indicators

token_technical_indicators
Read-onlyIdempotent

Get a technical-analysis snapshot for a token: SMA(20/50/200), EMA(12/26) and EMA(20/50/200), RSI(14), MACD(12,26,9), Bollinger Bands(20, 2σ), ATR(14), and rolling VWAP(20), computed from the last 1,000 closed candles at an explicit timeframe.

Supports EVM chains and Solana for on-chain tokens, AND Hyperliquid perpetual futures. For Hyperliquid perps, pass chain="hyperliquid" and use the perp symbol as tokenAddress (e.g. "BTC", "HYPE" for native perps; "XYZ:ORDI" for XYZ-namespaced perps — prefix is normalized automatically).

YOU MUST USE THIS for technical analysis instead of computing indicators from raw token_ohlcv candles — it uses far more history (1,000 closed candles) and charting-platform conventions (SMA-seeded EMA, Wilder RSI/ATR, population-σ Bollinger).

Timeframes (explicit, no auto-resolution):

  • 5m / 15m / 30m / 1h / 4h: intraday and short-horizon analysis

  • 1d (default): swing/position horizon

  • 1w: long-term trend

Output: a snapshot header (candles used, date range, last close, 5-candle price change) plus one row per indicator, each with a 5-candle trend delta so you can read direction, not just level:

  • SMA 20/50/200: values, price vs each, MA slopes

  • EMA 12/26: values, spread %, widening/narrowing

  • EMA 20/50/200: values, price vs each

  • RSI(14): level, prior candle, 5-candle change

  • MACD(12,26,9): line/signal/histogram, rising/falling, candles since signal cross

  • Bollinger(20,2σ): bands, %B, bandwidth and its change

  • ATR(14): value and % of price (volatility), rising/falling

  • VWAP(20): value, price vs VWAP

Indicators without enough closed-candle history render as n/a (e.g. SMA200 on young tokens); the candle count used is always reported. VWAP is n/a on Hyperliquid 5m-1h timeframes (volume is NULL in those views) — use 4h or 1d for Hyperliquid VWAP.

Example Usage: Daily technical snapshot for WETH: { "chain": "ethereum", "tokenAddress": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2", "timeframe": "1d" }

4-hour snapshot for the BTC Hyperliquid perp:
```
{
    "chain": "hyperliquid",
    "tokenAddress": "BTC",
    "timeframe": "4h"
}
```

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": {
      "request": "<request>"
    },
    "name": "token_technical_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRequest for the token_technical_indicators tool (explicit timeframe, always computed up to now — no date range).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / request / properties / chain / description
      Added value: +"Blockchain network for the token. Use the chain returned by general_search."
    • addedInput schema / properties / request / properties / tokenAddress / description
      Added value: +"Token contract address or Solana mint address. Use general_search to resolve a token name to its address and chain. For a tool with a perps mode, use the Hyperliquid coin symbol in that mode."
  2. Changed6 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "description": "Request for the token_technical_indicators tool (explicit timeframe,\nalways computed up to now — no date range).",
      -    "properties": {
      -      "chain": {
      -        "type": "string"
      -      },
      -      "timeframe": {
      -        "default": "1d",
      -        "description": "Candle timeframe for the indicator computation: 5m, 15m, 30m, 1h, 4h, 1d, or 1w. Default: 1d.",
      -        "enum": [
      -          "5m",
      -          "15m",
      -          "30m",
      -          "1h",
      -          "4h",
      -          "1d",
      -          "1w"
      -        ],
      -        "type": "string"
      -      },
      -      "tokenAddress": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "chain",
      -      "tokenAddress"
      -    ],
      -    "type": "object"
      -  }
      -]
    • addedInput schema / properties / request / description
      Added value: +"Request for the token_technical_indicators tool (explicit timeframe,\nalways computed up to now — no date range)."
    • addedInput schema / properties / request / properties
      Added value: +{
      +  "chain": {
      +    "type": "string"
      +  },
      +  "timeframe": {
      +    "default": "1d",
      +    "description": "Candle timeframe for the indicator computation: 5m, 15m, 30m, 1h, 4h, 1d, or 1w. Default: 1d.",
      +    "enum": [
      +      "5m",
      +      "15m",
      +      "30m",
      +      "1h",
      +      "4h",
      +      "1d",
      +      "1w"
      +    ],
      +    "type": "string"
      +  },
      +  "tokenAddress": {
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / request / required
      Added value: +[
      +  "chain",
      +  "tokenAddress"
      +]
    • addedInput schema / properties / request / type
      Added value: +"object"
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: computation window (last 1,000 closed candles), no auto-resolution of timeframe, n/a behavior for insufficient history with candle count always reported, and the Hyperliquid VWAP limitation at 5m–1h because volume is NULL. These are exactly the operational caveats an agent needs.

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 cleanly sectioned into MUST-USE guidance, timeframes, output, and caveats, plus two concrete examples. It is long, and the per-indicator output enumeration is partly redundant given an output schema exists, which keeps it from a 5.

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 nested-request tool with an output schema, it covers everything an agent must know: no date range (always computed to now), explicit timeframe default, perp support, insufficient-history handling, and a documented degradation (Hyperliquid VWAP). No gaps that would cause a misinvocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3; the description goes beyond it by explaining the perp mode (chain="hyperliquid" with the coin symbol as tokenAddress), namespaced symbols like "XYZ:ORDI" with automatic prefix normalization, and what each timeframe is suited for. It stops short of describing tokenAddress format edge cases for EVM vs Solana beyond the schema text.

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?

Opens with a specific verb+resource ("Get a technical-analysis snapshot for a token") and enumerates the exact indicator set and their parameters (SMA 20/50/200, RSI(14), MACD(12,26,9), Bollinger(20,2σ)), so an agent instantly knows what it returns and can distinguish it from token_ohlcv or token_quant_scores.

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

Usage Guidelines5/5

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

Explicitly names the alternative and the condition for choosing this tool: "YOU MUST USE THIS ... instead of computing indicators from raw token_ohlcv candles," with the reason (1,000 candles of history, charting-platform conventions). It further maps timeframes to horizons (5m–4h intraday, 1d swing, 1w long-term), which is actionable when-to-use routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources