Skip to main content
Glama

Technical indicators for one crypto pair and interval

crypto_indicators
Read-only

Technical indicators for one crypto pair and interval, computed from the last 60 to 300 candles: SMA and EMA for the periods you give (default SMA 20, 50, 200; EMA 12, 26), RSI 14 (Wilder), MACD 12/26/9, Bollinger 20/2, ATR 14, the latest values, and a plain trend note (above or below the 200 average, overbought or oversold). Candles come from Coinbase; the newest candle may still be forming. Information only, not financial advice. Related tools on this server, for a different need: crypto_candles when you need OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m; crypto_orderbook when you need a level-2 order book snapshot for a Coinbase pair: best bid. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "pair": "<pair>"
    },
    "name": "crypto_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
emaNoComma-separated EMA periods, up to 5, each 2 to 200 (default 12,26)
smaNoComma-separated SMA periods, up to 5, each 2 to 200 (default 20,50,200)
pairYesCoinbase pair like BTC-USD or ETH-USD
limitNoCandles to use, 60 to 300, default 300
granularityNoCandle size: 1m, 5m, 15m, 1h (default), 6h or 1d

Output Schema

NameRequiredDescriptionDefault
emaNo
smaNo
macdNo
pairNo
atr14No
priceNo
rsi14No
trendNo
sourceNo
candlesNo
bollingerNo
checkedAtNo
disclaimerNo
lastCandleNo
granularityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the data source (Coinbase), a data-freshness caveat ('the newest candle may still be forming'), the computation window (last 60-300 candles), pricing ($0.002 per successful call via x402) and that failed calls are not charged. These are exactly the behavioral traits annotations cannot convey.

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?

Purpose and indicator list are front-loaded, and the trailing pricing/disclaimer sentences earn their place for a paid tool. The indicator cluster is one long run-on sentence with heavy comma splicing, which costs a little readability but no real waste.

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?

Output schema already covers return shape, and the description fills the remaining gaps an agent needs: data source, candle-count window, the still-forming-candle caveat, and the x402 payment model with its charge policy. Nothing material is missing for a 5-parameter read-only tool.

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 coverage is 100%, so baseline is 3. The description restates the SMA/EMA defaults already documented in the schema and does not add meaning for 'limit' or 'granularity' beyond what the schema says, so it neither compensates for nor extends the structured fields.

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 and resource ('technical indicators for one crypto pair and interval') and then enumerates exactly which indicators are returned (SMA, EMA, RSI 14 Wilder, MACD 12/26/9, Bollinger 20/2, ATR 14, latest values, trend note). This is far more than a restatement of the name and lets an agent decide without opening the schema.

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?

It explicitly routes the agent away from this tool for adjacent needs: 'crypto_candles when you need OHLCV candles ... crypto_orderbook when you need a level-2 order book snapshot.' Both the alternative and the condition that selects it are named, which is the top tier for this dimension.

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