Skip to main content
Glama

AINDEX

Indicators and trend

technical_analysis
Read-only

RSI with divergence, MACD, EMA 9/21/50/200, SMA 20/50/200, Bollinger, ATR with its percentile, ADX with +DI/-DI, stochastic with KDJ, CCI, VWAP (anchored and rolling), OBV and volume against its average for a market, with a trend call per timeframe (default 1h, 4h and 1d) and whether they agree. Computed by AINDEX from the market's candles.

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>"
    },
    "name": "technical_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueNo
symbolYes
timeframesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully adds provenance (computed by AINDEX from the market's candles) and the default timeframe trio, but says nothing about cost, rate limits, behavior on unsupported symbol/venue combinations, or how disagreements between timeframes are expressed.

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?

It is one dense sentence with no filler; the long indicator enumeration is information-bearing for a tool whose value is precisely that breadth. The weakness is that it opens with a list of indicators rather than a leading statement of what the tool returns, making it harder to scan.

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?

No output schema exists, so the description should convey more about the response shape — e.g., how per-timeframe trend calls and indicator values are returned, and what a timeframe-agreement flag looks like. It covers inputs' defaults and data provenance but leaves the result structure for the agent to discover.

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 0%, so the description must compensate and it only partially does: it documents the default for `timeframes` (1h, 4h, 1d), which is unavailable in the schema. It says nothing about `symbol` format expectations (beyond the pattern), or what `venue` changes, leaving two of three parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly what is computed (RSI with divergence, MACD, EMA/SMA sets, Bollinger, ATR percentile, ADX/DI, KDJ, CCI, VWAP, OBV, volume vs. average) plus a per-timeframe trend call, which makes it unambiguously distinct from get_candles, get_levels, and get_patterns. It never states the purpose in a single verb-led sentence, but the resource is concrete enough to act on.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no reference to alternatives such as computing indicators from raw candles via get_candles. The only usage-flavored signal is the default timeframe set, which is replicated defaulting behavior rather than routing guidance.

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