Avanza MCP Server

Overview Schema Source Related Servers Discussions Admin

get_fund_chart

Read-onlyIdempotent

Retrieve raw fund chart data points in source order for a chosen time period, using offset and limit to paginate without aggregation.

Instructions

Get a page of raw fund dataSerie points in source order, without aggregation.

x/y values retain upstream meaning; y is not assumed to be NAV or a return. Offset/limit slice the chosen period; dates describe the full source period.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Fund chart data with historical performance.
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.0Sep 29, 2026
- removedOutput schema / properties / data / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / data / properties / dataSerie / items / additionalProperties
```
Removed value: -true
```

Changed10 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": 100,
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

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 / properties / time_period / enum

Previous value: -[
-  "one_week",
-  "one_month",
-  "three_months",
-  "one_year",
-  "three_years",
-  "five_years",
-  "this_year"
-]New value: +[
+  "one_week",
+  "one_month",
+  "three_months",
+  "this_year",
+  "one_year",
+  "three_years",
+  "five_years"
+]

changedInput schema / required

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

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

addedOutput schema / properties

Added value: +{
+  "data": {
+    "additionalProperties": true,
+    "description": "Fund chart data with historical performance.",
+    "properties": {
+      "dataSerie": {
+        "items": {
+          "additionalProperties": true,
+          "description": "Single data point in fund chart.",
+          "properties": {
+            "x": {
+              "type": "integer"
+            },
+            "y": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "x",
+            "y"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "fromDate": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "toDate": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      }
+    },
+    "required": [
+      "id",
+      "dataSerie"
+    ],
+    "type": "object"
+  },
+  "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"
+  }
+}

addedOutput schema / required

Added value: +[
+  "data",
+  "pagination"
+]

First observedv0.1.0Feb 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds valuable context beyond that: values come in source order, x/y retain upstream meaning, y is not assumed to be NAV or a return, and offset/limit slice within the chosen period. This is genuinely useful data-semantics disclosure.

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?

Three sentences, front-loaded with the core purpose before nuance. Most sentences earn their place, though 'dates describe the full source period' is terse to the point of ambiguity.

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?

An output schema exists so return values needn't be described, and annotations carry the safety profile. The description covers pagination and value semantics, but omits the routing relationship with get_fund_chart_periods and any guidance on time_period values, which are the main remaining gaps.

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 only 25% (only order_book_id documented), so the description must help. It clarifies that offset/limit slice the chosen period and that dates describe the full source period, which adds meaning. However, the time_period enum values and their interaction with pagination are never explained, leaving a notable gap.

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?

States a specific verb and resource ('Get a page of raw fund dataSerie points in source order, without aggregation'), which clearly conveys a raw paginated read. It does not, however, name or differentiate from the obvious sibling get_fund_chart_periods, so an agent cannot fully disambiguate without opening both schemas.

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?

The phrase 'without aggregation' and 'raw ... points' implies this is the tool for raw time-series data rather than summarized views, giving implied usage guidance. But there is no explicit when-to-use statement, no exclusions, and no reference to get_fund_chart_periods as the alternative for listing available periods.

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