TipRanks

get_assets_data

Read-onlyIdempotent

Returns key TipRanks stock data for one or more tickers.

Args:
    tickers: Ticker symbols — a comma-separated string ("AAPL,MSFT,C") or a
        JSON array (["AAPL","MSFT","C"]). Both are accepted.

Returns JSON {"assetsData": [...one compact entry per ticker...]}. This is a
headline summary tuned to stay small enough for a whole portfolio to fit in a
single response. Fields per entry:
  - ticker, companyName, sector, stockType, marketCap
  - url: canonical TipRanks page for the stock — use as the citation source.
  - price: latest close.
  - smartScore: TipRanks composite 1-10 (combines the 8 datasets — analyst,
      blogger, news, hedge-fund, insider, etc.).
  - analystConsensus / bestAnalystConsensus: rating label from ALL covering
      analysts vs. the top-performing ones ("Strong Buy".."Strong Sell"); a
      divergence between the two is itself a signal.
  - priceTarget: average 12-month target. priceTargetUpside: decimal vs.
      current price (0.05 = +5%).
  - peRatio, dividendYield (decimal).
  - newsSentiment, hedgeFundsScore, insiderScore: 0-1 sentiment signals.
  - ytdGainPct, yearlyGainPct: price performance as a percent (12.5 = +12.5%,
      3944 = +3944%).
  - nextEarningsDate, and daysUntilEarnings (whole days from today — quote this
      rather than computing the gap from the date yourself).
Floats are rounded and dates are day-resolution. For deeper per-ticker detail
(full price history, 13F / insider breakdowns, blogger counts, financials)
use the dedicated tools (get_stock_prices, get_hedge_fund_holdings,
get_insider_transactions, get_financials, ...).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tickers`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_assets_dataOutput",
-  "type": "object"
-}New value: +null

First observedJul 21, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already mark readOnlyHint=true, destructiveHint=false. The description adds orthogonal behavioral details: response size is 'tuned to stay small enough for a whole portfolio,' floats are rounded, dates are day-resolution, and it instructs agents to 'quote daysUntilEarnings rather than computing the gap.' No contradiction.

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?

Although long, the description is well-structured: a one-sentence summary, input format, return wrapper, and a bulleted field list. Every line adds value—required to document the many output fields. Front-loaded with the core purpose and followed by logically grouped details.

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 one parameter and no output schema, the description covers everything: input format, full field semantics, return structure, and guidance on when to use sibling tools. It is complete enough for an agent to invoke and interpret results without additional lookups.

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

Parameters5/5

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

Schema only says 'tickers' is string or array with no description (0% coverage). The description compensates fully: 'a comma-separated string ("AAPL,MSFT,C") or a JSON array (["AAPL","MSFT","C"]). Both are accepted.' This adds crucial format details beyond the schema.

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 a clear, specific statement: 'Returns key TipRanks stock data for one or more tickers.' It enumerates the fields returned, distinguishing it from sibling tools by describing it as a compact portfolio-level summary.

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 states when not to use: 'For deeper per-ticker detail ... use the dedicated tools (get_stock_prices, get_hedge_fund_holdings, get_insider_transactions, get_financials, ...).' This gives clear alternatives and context for when the tool is appropriate.

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

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

Need Help?