TipRanks

get_technical_analysis

Read-onlyIdempotent

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

Stocks only — ETFs like SPY, QQQ, VTI are not supported here. For ETFs,
use get_etf_analysis, get_etf_forecast, get_etf_top_stocks, or
get_etf_exposures instead.

Args:
    tickers: Comma-separated stock tickers (e.g. 'NVDA' or 'NVDA,AAPL').
             ETF tickers will return no data.
    timeFrame: '1m','5m','15m','30m','1h','5h','day','3d','week','2w','month' (default: 'day')

Returns: summary scores, oscillators (RSI, MACD, Stochastics, ADX, CCI,
         Williams %R, ATR, ROC), moving averages, and pivot points.
         indicator field: 1=Sell, 2=Neutral, 3=Buy.
         scoreScale: 1=StrongBuy, 2=Buy, 3=Neutral, 4=Sell, 5=StrongSell.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tickers`	Yes
`timeFrame`	No	One of '1m','5m','15m','30m','1h','5h','day','3d','week','2w','month' (default: 'day')	day

TDQS

A4.7/5.0

Behavior4/5

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

With annotations already declaring readOnlyHint, idempotentHint, and non-destructive behavior, the description adds meaningful context: ETF tickers return no data, and it documents the return structure including indicator and scoreScale semantic scales. This exceeds the low bar set by 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: purpose, usage limitation, args, and returns. Each section is concise and front-loaded. It avoids fluff and every sentence provides actionable information.

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?

Given there is no output schema, the description adequately explains what is returned, the meaning of indicator (1=Sell, 2=Neutral, 3=Buy) and scoreScale (1=StrongBuy...5=StrongSell). It also covers the ETF restriction and default timeframe, making it fully sufficient for an agent to invoke correctly.

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%; the description fills the gap for 'tickers' by specifying comma-separated format, examples, and the ETF exclusion behavior. The 'timeFrame' parameter repeats the schema's list, so marginal value is added only for tickers, warranting a strong but not perfect score.

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 opens with specific outputs (RSI, MACD, Stochastics, etc.) and clearly states it applies to 'individual stocks' only. It explicitly differentiates from ETF-related siblings by naming alternative tools, making the purpose unambiguous.

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 states when NOT to use (ETFs not supported) and provides a list of alternative tools (get_etf_analysis, get_etf_forecast, etc.). It also warns that ETF tickers return no data, giving clear go/no-go guidance.

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

All TipRanks tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation3/5

Many tools have overlapping purposes, e.g. get_etf_analysis vs get_etf_forecast both provide ETF analyst consensus, get_etf_holdings vs get_etf_top_stocks both list constituents, and get_portfolio_overview vs get_portfolio_performance both return returns/performance. The detailed descriptions help, but the sheer number of similar tools creates ambiguity in selection.

Naming Consistency4/5

The set is largely consistent with a 'get_' prefix and descriptive nouns (get_stock_quotes, get_crypto_quote, get_dividend_history). Minor deviations include 'list_my_portfolios' instead of 'get_my_portfolios' and singular/plural variants like get_all_commodities_quotes vs get_commodity_quote, but the pattern remains predictable.

Tool Count1/5

With 71 tools, the count far exceeds the 50+ threshold described as an extreme mismatch. Even though the server covers a broad financial domain, such a large surface is overwhelming for an agent and includes many redundant or highly specific tools that could be consolidated.

Completeness5/5

The tool set provides comprehensive coverage of TipRanks data: quotes and historical data for all major asset classes, news, earnings and economic calendars, analyst and sentiment data, financial statements, technical analysis, options, portfolios, and screeners. There are no obvious dead ends for typical financial research tasks.

Resources

Need Help?