Skip to main content
Glama

TipRanks

by com.tipranks
OverviewDiscussions(1)Admin

get_technical_analysis

Read-onlyIdempotent

Returns RSI, MACD, Stochastics, ADX, moving averages, and pivot points for stocks and ETFs.

Covers stocks and ETFs alike (e.g. 'NVDA', 'SPY', 'QQQ', 'VTI') with the
same payload shape. For an ETF's analyst consensus, forecast, holdings or
exposures, use get_etf_analysis, get_etf_forecast, get_etf_top_stocks, or
get_etf_exposures.

Args:
    tickers: Comma-separated stock or ETF tickers (e.g. 'NVDA' or 'NVDA,SPY').
    timeFrame: '1m','5m','15m','30m','1h','5h','day','3d','week','2w','month' (default: 'day')
        '5h' is slow upstream: request it for one ticker per call.

Returns: summary scores, oscillators (RSI, MACD, Stochastics, ADX, CCI,
         Williams %R, ATR, ROC), moving averages, and pivot points.
         Labels are strings. indicator: "Buy", "Neutral" or "Sell" (null
         on ATR and pivot points). scoreScale: "StrongBuy", "Buy",
         "Neutral", "Sell" or "StongSell" (the upstream's own spelling).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickersYes
timeFrameNoOne of '1m','5m','15m','30m','1h','5h','day','3d','week','2w','month' (default: 'day'). Request '5h' for one ticker per call.day

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / timeFrame / description
      Previous value: -"One of '1m','5m','15m','30m','1h','5h','day','3d','week','2w','month' (default: 'day')"New value: +"One of '1m','5m','15m','30m','1h','5h','day','3d','week','2w','month' (default: 'day'). Request '5h' for one ticker per call."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_technical_analysisOutput",
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real operational context beyond them: the '5h' upstream latency warning, consistent payload shape across stocks and ETFs, and null-handling for indicators on ATR/pivot points. It does not discuss pagination or error behavior, so 4.

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 and followed by clearly separated Args/Returns sections; every block earns its place. It is somewhat verbose and carries a typo ('StongSell'), which is a minor blemish against an otherwise tight structure.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so thoroughly (indicator lists, label strings, scoreScale values, null cases). Combined with parameter explanations and sibling routing, an agent has nearly everything needed to call it correctly; only raw-price sibling differentiation is absent.

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 coverage is 50% (timeFrame documented, tickers undocumented), so the description must compensate. It does: it explains tickers as comma-separated stock/ETF symbols with concrete examples and restates the timeFrame enum plus the '5h' caveat, adding meaning not present in the schema for the required parameter.

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?

The description states a specific resource (technical indicators) and enumerates the exact outputs (RSI, MACD, Stochastics, ADX, moving averages, pivot points) for a defined asset universe (stocks and ETFs). It explicitly routes related-but-different ETF requests to named siblings, so an agent can distinguish it without opening any schema.

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?

It names the alternative tools (get_etf_analysis, get_etf_forecast, get_etf_top_stocks, get_etf_exposures) and the condition (ETF analyst consensus, forecast, holdings, exposures) that selects them. It also flags an operational exclusion ('5h' slow upstream, one ticker per call). It stops short of contrasting against raw-price siblings like get_stock_prices, so a 4 rather than 5.

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

All TipRanks toolsInspect
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