Avanza MCP Server

Overview Schema Source Related Servers Discussions Admin

get_dividends

Read-onlyIdempotent

Retrieve a Swedish stock's dividend history by financial year, including dividend per share, direct yield ratio, or payout ratio, using an Avanza order-book ID.

Instructions

Page one dividendsByYear metric: dividendPerShare, directYieldRatio or dividendPayoutRatio.

data preserves the upstream section name. Missing data is omitted, not an empty history. Records contain financialYear, reportType, value and optional date, not inferred ex/payment dates. available_metrics lists names only; sibling series are excluded. Units and scales are upstream-defined.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`metric`	Yes
`offset`	No
`order_book_id`	Yes	Avanza order-book ID from discovery; not the separate instrumentId.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`metric`	Yes
`selection`	Yes
`pagination`	Yes
`available_metrics`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.1.0Sep 29, 2026

changedOutput schema / properties / data / additionalProperties / anyOf

Previous value: -[
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {
-          "items": {
-            "additionalProperties": true,
-            "description": "Observed upstream point fields. Values retain their source-specific scale.",
-            "properties": {
-              "date": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "default": null
-              },
-              "financialYear": {
-                "type": "integer"
-              },
-              "reportType": {
-                "type": "string"
-              },
-              "value": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "required": [
-              "reportType",
-              "financialYear",
-              "value"
-            ],
-            "type": "object"
-          },
-          "type": "array"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "items": {
+            "description": "Observed upstream point fields. Values retain their source-specific scale.",
+            "properties": {
+              "date": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "default": null
+              },
+              "financialYear": {
+                "type": "integer"
+              },
+              "reportType": {
+                "type": "string"
+              },
+              "value": {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "required": [
+              "reportType",
+              "financialYear",
+              "value"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed11 schema fields changedv2.0.0Sep 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / instrument_id
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / limit

Added value: +{
+  "default": 20,
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / metric

Added value: +{
+  "maxLength": 100,
+  "minLength": 1,
+  "pattern": "^[A-Za-z][A-Za-z0-9]*$",
+  "type": "string"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / order_book_id

Added value: +{
+  "description": "Avanza order-book ID from discovery; not the separate instrumentId.",
+  "minLength": 1,
+  "pattern": "^[0-9]+$",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "instrument_id"
-]New value: +[
+  "order_book_id",
+  "metric"
+]

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"One named metric in one selected section, without sibling series or summaries."

addedOutput schema / properties

Added value: +{
+  "available_metrics": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "data": {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "additionalProperties": {
+            "anyOf": [
+              {
+                "items": {
+                  "additionalProperties": true,
+                  "description": "Observed upstream point fields. Values retain their source-specific scale.",
+                  "properties": {
+                    "date": {
+                      "anyOf": [
+                        {
+                          "type": "string"
+                        },
+                        {
+                          "type": "null"
+                        }
+                      ],
+                      "default": null
+                    },
+                    "financialYear": {
+                      "type": "integer"
+                    },
+                    "reportType": {
+                      "type": "string"
+                    },
+                    "value": {
+                      "anyOf": [
+                        {
+                          "type": "number"
+                        },
+                        {
+                          "type": "null"
+                        }
+                      ]
+                    }
+                  },
+                  "required": [
+                    "reportType",
+                    "financialYear",
+                    "value"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "object"
+  },
+  "metric": {
+    "type": "string"
+  },
+  "pagination": {
+    "properties": {
+      "has_more": {
+        "type": "boolean"
+      },
+      "limit": {
+        "maximum": 100,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "offset": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "returned": {
+        "type": "integer"
+      },
+      "total": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Source count; null when the selected section is unavailable"
+      }
+    },
+    "required": [
+      "offset",
+      "limit",
+      "total",
+      "returned",
+      "has_more"
+    ],
+    "type": "object"
+  },
+  "selection": {
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "selection",
+  "metric",
+  "available_metrics",
+  "data",
+  "pagination"
+]

First observedv0.1.0Feb 4, 2026

TDQS

A3.5/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), but the description adds substantive behavioral context: missing data is omitted rather than returned as an empty history, records carry financialYear/reportType/value/optional date, returned dates are not inferred ex/payment dates, and units are upstream-defined. This goes meaningfully beyond the structured hints.

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?

The core purpose is front-loaded in the first sentence, followed by dense but useful caveats. There is minor redundancy (returned-record description overlaps what the output schema already provides), but overall it is efficient and earns its space.

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 plus full read-only annotations, the description is not required to explain return shapes or safety, yet it still covers paging, missing-data behavior, field contents, and units. Only the absence of any usage routing keeps it from being fully complete.

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 coverage is only 25%, so the description must compensate. It does clarify the metric parameter by enumerating allowed metric names and describes the returned record fields, but it adds nothing for limit/offset beyond the schema defaults, and the upstream-defined units caveat is vague rather than actionable.

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 a specific resource (dividendsByYear) and the exact metric options (dividendPerShare, directYieldRatio, dividendPayoutRatio), so an agent can tell it retrieves dividend-per-share style data. It doesn't explicitly contrast itself with sibling tools like get_company_financials, which weakens sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative like get_company_financials. The note about available_metrics implying discovery is the closest thing to routing context, but it never states when this tool should be chosen.

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