Leeway Financial Data

dividends

dividends

Read-only

Dividends for SYMBOL.EXCHANGE. view=latest is the dividend events, with date, declarationDate, paymentDate, period, value, unadjustedValue, and currency. calculations=true on that view adds stockprice and yield, where yield is unadjustedValue divided by stockprice. view=history is one point per trading day, with date, open, high, low, and close. A zero means no dividend is active that day. For split ratios, use splits. Costs 2 request units.

Input Schema

Name	Required	Description
`to`	No	YYYY-MM-DD. The end date.
`from`	No	Format: YYYY-MM-DD. The start date.
`view`	Yes	latest is dividend events. history is the daily yield series.
`calculations`	No	Format: Boolean. If true, returns price at Ex-Div date as well as dividend payout ratio.
`symbolExchange`	Yes	Symbol and Exchange. Example: SAP.XETRA

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 20, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / view

Added value: +{
+  "description": "latest is dividend events. history is the daily yield series.",
+  "enum": [
+    "latest",
+    "history"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "symbolExchange"
-]New value: +[
+  "view",
+  "symbolExchange"
+]

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "result": {
-      "anyOf": [
-        {
-          "items": {
-            "anyOf": [
-              {
-                "additionalProperties": {},
-                "properties": {
-                  "currency": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "date": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "declarationDate": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "paymentDate": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "period": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "unadjustedValue": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "value": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  }
-                },
-                "type": "object"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          "type": "array"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object"
-}New value: +null

First observedOct 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the return fields for each view, the meaning of a zero value, calculations=true behavior and yield formula, and the cost of 2 request units. These details materially help an agent understand the output and cost profile.

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?

The description is front-loaded with the resource and identifier, then proceeds through view semantics, calculations, history behavior, exclusions, and cost with no filler. Every sentence carries useful operational information.

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

Completeness5/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 compensates by specifying return fields for both views, zero-value semantics, calculation behavior, and request cost. It also names an alternative for split data, making the definition complete for an agent to call it correctly.

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 schema already documents all parameters. The description still adds value by elaborating on view behavior, calculations=true output, and the yield formula, though it does not add meaning for from, to, or symbolExchange beyond the schema.

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 opening phrase 'Dividends for SYMBOL.EXCHANGE' names the resource and identifier format, and 'For split ratios, use splits' distinguishes it from a sibling tool. It lacks an explicit verb such as 'retrieve', but the purpose is still clear from the view descriptions.

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 explains when to use view=latest versus view=history and explicitly routes split-ratio needs to the splits tool. It does not address other nearby alternatives (e.g. prices for stock prices) or state broader exclusions, so it is strong but not exhaustive.

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

All Leeway Financial Data tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?