TipRanks

get_dividend_history

Read-onlyIdempotent

Dividend payment history for a ticker. Chart-ready: includes the current snapshot (yield %, payout ratio, frequency, annualised payout) plus two time series — a per-payment list [{ex_date, pay_date, amount, yield_pct, is_special, ...}] (newest first, capped at count) and an annual_totals list [{year, amount, yield_pct}] suitable for a yearly bar chart.

All yields are emitted as percentages (4.5 = 4.5%), so plots don't
need to know which underlying field used decimal vs. percentage
encoding.

Use for: "AAPL dividend history", "yield trend over 5 years",
"dividend growth chart", "is the payout sustainable".

Args:
    ticker: Stock ticker (e.g. 'AAPL', 'JNJ').
    count: Number of most-recent individual payments to return
            (default 16, max 100). The annual_totals series is
            always returned in full.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`ticker`	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_dividend_historyOutput",
-  "type": "object"
-}New value: +null

First observedJul 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate read-only/idempotent, and the description adds significant behavioral context: output structure, yield percentage format (4.5 = 4.5%), per-payment list capped at 'count', and annual_totals always returned in full. No contradictions with 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-organized: purpose first, then output structure, then yield encoding, use cases, and argument details. Every sentence adds value, and the formatting with headings/paragraphs makes it easy to scan.

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 no output schema, the description thoroughly explains the return shape (snapshot, per-payment list, annual totals) and edge behavior (count cap, yield percentages). It sufficiently covers the tool's functionality for an agent to select and invoke it correctly.

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 coverage is 0% with no descriptions for ticker or count. The description compensates by explaining ticker with examples and count with default (16) and max (100), plus the effect on annual_totals. This adds meaningful semantics 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 explicitly states 'Dividend payment history for a ticker' and details the output components (current snapshot, per-payment list, annual totals). This clearly distinguishes it from siblings like get_stock_splits or get_earnings_history.

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?

Provides clear usage examples ('Use for: AAPL dividend history', 'yield trend over 5 years') and describes the nature of the data. However, it does not explicitly mention when not to use this tool or direct users to alternative tools, so it stops short of full exclusion 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

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?