Skip to main content
Glama

Dividend History

GetDividendHistory
Read-only

Get the stored cash dividends of an exact stock or ETF listing, newest first. Each row gives the ex-dividend date and cash amount per share: in USD for a US listing, and in the listing's trading currency for a listing on another exchange (MIC:TICKER). Amounts are as the data source states them today: a dividend paid before a later split is normally restated to the post-split share count, so it can differ from the amount declared at the time. Date filters apply to the ex-dividend date. Future ex-dates can appear after a dividend is declared. Each listing reports its own payments: a share class (BRK-A beside BRK-B) or a fund series sharing its trust's filer (SCHD beside FNDA) never inherits another listing's dividends.

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": "GetDividendHistory"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoNumber of newest matching records to skip for pagination (default: 0).
tickerYesListed stock or ETF ticker (e.g., AAPL, BRK-A, SCHD); a listing on another exchange is MIC:TICKER (XPAR:AIR).
endDateNoOptional latest ex-dividend date in YYYY-MM-DD format.
startDateNoOptional earliest ex-dividend date in YYYY-MM-DD format.
maxResultsNoMaximum number of records to return (default: 20, max: 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Listed stock or ETF ticker (e.g., AAPL, BRK-A, SCHD)."New value: +"Listed stock or ETF ticker (e.g., AAPL, BRK-A, SCHD); a listing on another exchange is MIC:TICKER (XPAR:AIR)."
  2. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Current primary stock ticker (e.g., AAPL, MSFT)."New value: +"Listed stock or ETF ticker (e.g., AAPL, BRK-A, SCHD)."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavior: return ordering, currency semantics by listing, split-restatement of historical amounts, date-filter behavior, future ex-dates, and per-listing isolation. These details materially help an agent interpret and trust the results.

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 purpose is front-loaded, and each sentence adds relevant scoping, currency, restatement, date-filter, or listing-isolation information. Despite its length, it is dense with useful distinctions and has no filler.

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?

For a dividend-history tool with no output schema, the description is complete: it explains row contents, currency behavior, restatement rules, date semantics, future events, and listing independence. The schema already covers pagination and bounds.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description reinforces the ticker and date-filter semantics but mostly aligns with what the schema already documents rather than adding substantial new parameter-level meaning.

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 gives a specific verb and resource: get stored cash dividends for an exact stock or ETF listing, returned newest first. It clearly distinguishes this tool from broader history tools by naming the precise data type and listing scope.

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 explains the relevant usage context: exact ticker or MIC:TICKER listing, date filters on ex-dividend date, and that future ex-dates may appear after declaration. It does not explicitly name alternatives or when-not-to-use cases, but the scope is clear enough for selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.