APIVerve

Dividends

Dividends

Read-only

Dividends: Dividends returns the dividend-per-share history for a US public company by ticker - the amount reported each quarter and year straight from official SEC filings - plus a derived dividend-growth summary with year-over-year growth, multi-year growth rates and a consecutive-years-of-growth streak calculated for you. Paid plans can add dividend yield and the full-year payout ratio. (Cost: 6 credits)

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

Input Schema

Name	Required	Description
`limit`	No	Number of periods to return in the history list (1-25). Defaults to 5.
`period`	No	Which series to return in the history list: quarterly (default) or annual.
`ticker`	Yes	Stock ticker symbol (e.g. AAPL, MSFT, KO)
`metrics`	No	Add a metrics block with the trailing annual dividend, dividend yield and payout ratio.

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds real behavior: data provenance (official SEC filings), that growth metrics are derived rather than raw, and that yield/payout ratio require a paid plan. It still omits error behavior for tickers with no dividend history and any rate-limit context beyond the credit price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The core purpose and the distinguishing details (source, derived summary, cost) are front-loaded, and the credit price is a useful trailing note. Minor waste in the redundant 'Dividends: Dividends' prefix and a slightly run-on first sentence.

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 an output schema present, the description need not describe the response shape, and it covers the remaining gaps an agent needs: US scope, SEC source, derived-vs-raw distinction, plan gating, and cost. Only edge-case behavior for zero-dividend tickers is left unstated.

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 all four parameters are documented in the schema itself, which sets the baseline at 3. The description contributes only indirectly by explaining that yield and payout ratio (the `metrics` block) are plan-gated; it never mentions `limit` or names the quarterly/annual `period` switch explicitly.

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?

States a specific verb and resource (returns dividend-per-share history by ticker) plus scope qualifiers that separate it from neighbors: US-only, official SEC filings source, and a derived growth summary. An agent can distinguish it from SECFilings or EarningsReport without opening the schema.

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?

Usage is only implied: the ticker is required and the data is US-only, which signals when it applies. There is no explicit when-to-use versus siblings (SECFilings, GlobalStockMarket, TickerNews) and no stated exclusions such as non-dividend-paying stocks or non-US issuers.

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

All APIVerve 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.