Skip to main content
Glama

AINDEX

Dividends and splits credited through stock-token multipliers

get_dividends
Read-only

How distributions have actually reached holders on chain. Robinhood stock tokens pay no cash: a distribution raises the token's multiplier. With no arguments: every token that has stepped, most received first. With token: its every step. Steps are not yields: pass-through varies by token, and splits are steps too.

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
limitNo
tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds substantive domain behavior beyond that: distributions arrive as multiplier increases rather than cash, results are ordered 'most received first,' and splits count as steps. It does not disclose volume of data returned or pagination behavior under the default limit.

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?

Four short sentences, each carrying distinct information, with the mechanism stated first and the call shapes after. No filler. The terse phrasing ('every token that has stepped,' 'its every step') is compact but slightly cryptic on first read.

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?

For a read-only, two-parameter tool with no output schema, the description covers what the data means, how results are ordered, and what the two call shapes return. It omits the result shape/fields and the role of the limit parameter, which are the remaining gaps an agent would want.

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 0%, so the description carries the burden. It fully explains the semantics of 'token' (returns that token's every step) and the no-argument case, but never mentions 'limit' (default 40, max 200) or the ordering interaction with it. Half the parameters gain meaning; one is left entirely to the schema's type and bounds.

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 specific resource and the mechanism: 'How distributions have actually reached holders on chain' via a token multiplier, and explicitly says 'Robinhood stock tokens pay no cash.' That distinguishes it from price/quote siblings without naming them. It never states a direct verb like 'list' or 'get', so the action is inferred rather than declared.

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?

It gives explicit mode selection: 'With no arguments: every token that has stepped' versus 'With token: its every step,' which is real when-to-use guidance for the two call shapes. It offers no exclusions or pointers to related tools such as get_token_market, and no guidance on when a caller should prefer this over a price or asset lookup.

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.

Resources