Skip to main content
Glama
Snapstock MCP Server

Snapstock MCP Server

by sorndotdev

Get annual dividend history

get_dividend_history
Read-only

Retrieve annual dividends per share, year-over-year changes, current yield, dividend streak, and next ex-date for a ticker to review dividend history and upcoming payments.

Instructions

Get annual dividends per share, year-over-year changes, current yield, streak, and the next ex-date for one ticker. Annual totals include special dividends. Dataset snapshot: 2026-11-15.

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_dividend_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker symbol, for example A, AAPL, KO, or JNJ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: annual totals include special dividends (a data-semantics decision an agent could otherwise misread) and a dataset snapshot date of 2026-11-15, which signals data freshness. It does not cover behavior for tickers lacking dividend records.

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, zero waste. The returned fields are front-loaded and the two qualifications (special dividends, snapshot date) follow compactly at the end.

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 usefully enumerates what comes back (per-share amounts, YoY changes, yield, streak, next ex-date), which is exactly the right compensation. Minor gap: 'streak' is not defined (presumably consecutive years of increases) and behavior for non-dividend-paying tickers is 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?

Only one parameter, and schema coverage is 100% with its own ticker example list, so the schema carries the burden. The description reinforces the single-ticker constraint but adds no format or validation detail beyond it — baseline 3 for a fully documented single param.

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 (Get) plus a precisely enumerated resource: annual dividends per share, YoY changes, current yield, streak, and next ex-date for one ticker. The single-ticker scope and dividend focus cleanly separate it from siblings like get_ticker_score and get_red_flags.

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?

Implies usage via 'for one ticker', making clear this is the single-ticker dividend lookup rather than a screening/list operation. However, no sibling is named, no exclusions are stated, and there is no guidance on what to do for a ticker with no dividend history.

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