Skip to main content
Glama

Dividends

get_dividends
Read-only

The dividends the user recorded, newest ex-dividend date first: the stock, ex-dividend and pay dates, the dividend per share, the shares, the amount, and what it added to cash. Recording and deleting dividends is done on the website or through the REST API.

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
toNoLatest ex-dividend date, YYYY-MM-DD.
fromNoEarliest ex-dividend date, YYYY-MM-DD.
limitNoPage size. Default 100.
marketNohk = Hong Kong, us = United States, cn = China A-shares.
offsetNoWhere the page starts; take next_offset from the previous answer. Default 0.
tickerNoFor example 0700.HK or 700 (hk), AAPL (us), 600519.SS or 600519 (cn).

Output Schema

NameRequiredDescriptionDefault
errorNo
limitNo
totalNo
offsetNo
warningsNo
dividendsNo
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. Beyond that the description adds genuinely useful behavior — results are sorted by newest ex-dividend date first and scoped to the user's own records — but it doesn't discuss pagination behavior (though the schema explains offset/limit) or volume/size limits.

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 tight sentences: the first front-loads the resource, sort order, and returned fields; the second front-loads the write-exclusion. No filler or repetition.

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 an output schema present, the description needn't explain return values, and annotations carry the safety profile; the description still adds sort order, user scoping, and the absence of write operations. What remains unstated — pagination workflow and result-size expectations — is minor and largely covered by the schema's offset/limit descriptions.

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 all six parameters, including the market enum and ticker formats, are already documented in the schema; the baseline of 3 applies. The description's mention of ex-dividend date ordering only lightly reinforces the semantics of from/to.

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?

The description names the resource precisely (the user's recorded dividends) and enumerates the returned fields — stock, ex-dividend and pay dates, dividend per share, shares, amount, and cash impact — so an agent knows exactly what this tool yields. The verb is implicit ("The dividends the user recorded") rather than an explicit "list"/"get", which is the only thing keeping it from 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?

It clearly states a usage boundary: recording and deleting dividends must be done on the website or via REST API, so the agent should not look for a write sibling here. There is no positive guidance on how to combine from/to/ticker/market filters or how to page with offset, which is left to the schema.

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.