Skip to main content
Glama

FinanceQuery

Dividend History

get_dividends
Read-onlyIdempotent

Get dividend history for one or more dividend-paying stocks (comma-separated symbols). A single symbol returns paginated dividend history plus analytics (CAGR, average payment, payout count); multiple symbols return a batch of dividend histories plus per-symbol errors (no analytics for batch).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum dividend payments per page; omitted = curated default (25)
rangeYesTime range: 1y|2y|5y|10y|max (default: max)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolsYesOne or more comma-separated ticker symbols (e.g., "AAPL" or "AAPL,KO,JNJ")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds genuine behavior on top: mode-dependent output shape, analytics only in single-symbol mode, and per-symbol errors in batch mode. That partial-failure disclosure is exactly what shapes an agent's invocation strategy. Sort order of the returned history and the error object shape are not disclosed.

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?

Two sentences, no filler, with the primary action front-loaded and the mode asymmetry packed into a single parenthetical. Every clause carries information the agent needs.

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 must carry the return-value burden and largely does: it names the analytics (CAGR, average payment, payout count), the paginated history, and per-symbol errors. Remaining gaps are minor but real: ordering of payments, whether `pageInfo` appears in both modes, and how a fully invalid symbol is reported outside batch mode.

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 description coverage is 100%, so range, limit, cursor, and fields are already fully documented, establishing a baseline of 3. The description adds the single-versus-multi semantics of `symbols`, but that is largely restated in the schema, and it says nothing extra about `range` defaults or `fields` selection behavior.

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?

Specific verb plus resource ('Get dividend history') scoped to 'dividend-paying stocks', with an explicit note that the input may be one or several comma-separated symbols. An agent knows exactly what data comes back. It stops short of naming or contrasting a sibling tool, which is the only thing keeping it off a 5.

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?

The definition routes the agent on the single most important decision: one symbol versus many, and states what each mode yields, so the caller can pick a mode deliberately rather than by trial. It gives no exclusions or prerequisites (e.g., whether non-dividend payers error or return empty), which would be needed for a 5.

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.