Portfolio Analytics MCP

Overview Schema Source Related Servers Discussions Admin

get_dividends

Read-only

Fetch dividend payments per share for a ticker and calculate the trailing-12-month total, using optional start and end dates to analyze distributions over a chosen period.

Instructions

Dividend payments per share for a ticker, plus a trailing-12-month total.

Amounts are per share as Yahoo reports them; this can be the fund's
distribution currency rather than the listing's trading currency (e.g. a
USD-distributing ETF listed in GBP), so check before computing a yield.

Args:
    ticker: Yahoo symbol.
    start_date: YYYY-MM-DD. Defaults to 2020-01-01.
    end_date: YYYY-MM-DD (exclusive).

Returns:
    `dividends` by date in the range with their `total` and `count`, plus
    `trailing_12m_total` and `payments_last_12m`; or an error dict.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_dividends"
  }
}

Input Schema

Name	Required	Default
`ticker`	Yes
`end_date`	No
`start_date`	No	2020-01-01

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description is not burdened with safety disclosure. It adds valuable behavior beyond that: amounts follow Yahoo's reporting currency, which may differ from the listing currency; end_date is exclusive; and errors are returned as an error dict.

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 summary is front-loaded and the Args/Returns structure is efficient. Every sentence adds useful information; there is no repetition of the schema or annotations.

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?

With no output schema, the description explains the return shape: per-date dividends with total and count, plus trailing_12m_total and payments_last_12m. Combined with full parameter documentation and the currency caveat, an agent has enough to call and interpret this tool 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 description coverage is 0%, so the description carries the full parameter burden. It documents all three parameters, including YYYY-MM-DD formats, the start_date default of 2020-01-01, and the exclusive end_date.

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 states a specific verb and resource: dividend payments per share for a ticker plus a trailing-12-month total. It is clear enough to distinguish from price-history and quote siblings, though it never names an alternative tool.

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

Usage Guidelines3/5

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

It implies the tool is used for dividend data and yield computation, and warns to check distribution currency before computing yield. However, it gives no explicit when-to-use/when-not-to-use guidance or named alternatives among the 20 sibling tools.

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