Skip to main content
Glama

Dividend data

get_dividends
Read-only

Returns a company's dividend data: yield, per-share amounts, growth, whether cash flow covers the payout, and the payments observed in its daily price history; projections never exceed the measured coverage. Without a symbol, returns the highest-yielding payers among the tracked companies and possible initiators. A company outside the ranking (a foreign issuer, for instance) returns the payments observed in its price history. Use it when the user asks whether a company pays a dividend, how much, or which companies yield the most. Estimates, not advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_dividends"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows in the ranking (default 20, max 60).
symbolNoTicker. Omit for the sector ranking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +60
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses that projections never exceed measured coverage, that out-of-ranking issuers fall back to price-history payments, and that results are estimates rather than advice. These are non-obvious behavioral traits an agent could not infer from the schema.

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?

Front-loaded with the return contents, then the no-symbol mode, then the fallback case, then usage and the disclaimer. Dense and mostly earning its place, though the middle fallback sentence and the final disclaimer could be trimmed slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the return-value burden and does so by enumerating the dividend fields and both ranking/fallback modes. Nothing critical is missing for correct invocation, though explicit return shape for the ranking case is only implied.

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

Parameters4/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, but the description earns more by explaining the semantic effect of omitting `symbol` (sector ranking of highest yielders and possible initiators) and by tying `limit` to ranking rows only.

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 plus the exact contents returned: yield, per-share amounts, growth, payout coverage, and observed payments. It also declares the two operating modes (symbol vs. no symbol), so an agent can distinguish it from every sibling, none of which covers dividends.

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?

Explicitly names the triggering user intents: whether a company pays a dividend, how much, or which companies yield the most. It gives clear context but does not name an alternative tool or state when not to use it.

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.