Avanza MCP Server

by AnteWall

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_fund_chart_periods

Read-onlyIdempotent

Retrieve available fund performance periods for a given Avanza order-book ID, excluding individual chart points.

Instructions

Get available fund performance periods, rather than individual chart points.

startDate is the source period start date. change retains its upstream scale; do not assume it uses the same scale as fund-guide development fields.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`periods`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed6 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 / 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"
+]

addedOutput schema / properties

Added value: +{
+  "periods": {
+    "items": {
+      "additionalProperties": true,
+      "description": "Fund performance for a specific time period.",
+      "properties": {
+        "change": {
+          "type": "number"
+        },
+        "startDate": {
+          "format": "date",
+          "type": "string"
+        },
+        "timePeriod": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "timePeriod",
+        "change",
+        "startDate"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "periods"
+]
```

First observedv0.1.0Feb 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds semantic context about returned startDate and change scale that goes beyond annotations, though it does not discuss permissions, rate limits, or pagination.

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 description is short and front-loads the purpose and sibling contrast in the first sentence. The second sentence adds dense caveats about startDate and change, which are not introduced by the input schema and slightly reduce immediate clarity, but it remains concise overall.

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, annotations cover the safety profile, and the sole input parameter is fully described in the schema. The description supplies the operation's scope and some output semantics, leaving an agent with enough to invoke it correctly; the unexplained startDate/change references are a minor gap.

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 100% for the sole order_book_id parameter, and the schema description already explains that it is an Avanza order-book ID, not an instrumentId. The tool description adds no input-parameter meaning; the startDate and change references are not input parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Get'), resource ('available fund performance periods'), and explicitly contrasts it with 'individual chart points', which distinguishes it from the sibling get_fund_chart. An agent can identify the operation without opening any schema.

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 gives clear context by implying that this tool should be used for period lists rather than chart points, which routes away from get_fund_chart. However, it does not explicitly name the alternative tool or state when a period list is preferable beyond the contrast, so it falls short of a full when/when-not/alternative prescription.

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